Scenario should provide access to a "World"

Currently it is possible to hook into and get the Scenario. It would be good if the scenario would allow to access the “World” like in js/ruby in the following way:

Provide access to the glue code instances created by cucumber

         /**
	 * Gets the current instance of the glue code in this scenario
	 * @param clazz glue code type
	 * @return returns the glue instance of the the given class or <code>null</code> if not defined in this scenario
	 */
	<T> T getGlue(Class<T> clazz); 

This would allow to communicate between glue-code steps without the need of any additional framework like picocontainer/spring.

[mpkorstanje]

https://github.com/cucumber/cucumber-jvm/issues/1711#issuecomment-516063549

Especially you want to support the “Specification Guys” so the don’t need to know what steps are there but can find a list on there hand, automatically generated from projects code.

And based on your earlier comment I think you might be misunderstanding what the purpose of Cucumber is. Cucumber is a collaboration tool, not an automated testing tool. Having multiple departments each providing step libraries that specification guys puzzle together would be the opposite of what Cucumber is intended to do.

https://cucumber.io/blog/the-worlds-most-misunderstood-collaboration-tool/

[mpkorstanje]

Cucumber is a framework to support BDD. Every feature added to the framework adds comes at a cost. A cost in terms of complexity, maintenance, documentation, usage, ect. This cost must be weighed against the benefit of the feature.

The feature you suggested is both highly technical, of use to exactly one user, and supports a use case that has been found to be detrimental to writing behaviour focused Gherkin. As such I see no benefit to adding it to Cucumber JVM. I’ve heard no new arguments since I closed this on Sep 22 so I’ll leave it at that.