[Spring] Deprecate cucumber.xml and implied context configuration #1940
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The prefered way to use
cucumber-spring
is to annotate a classwith both
@CucumberContextConfiguration
and a Spring contextconfiguration annotation such as
@ContextConfiguration
,@SpringBootTest
, ect.Cucumber currently supports the discovery of context
configuration on any step defintion class. This requires a
significant amount of code and intimate knowledge of the
Spring Framework.
By restricting this too only classes annotated with
@CucumberContextConfiguration
we can remove this complexity andsimply pass the annotated class to Spring
TestContextManager
framework.
If no context configuration is available Cucumber currently also
support reading the application context from a magical
cucumber.xml
file or should none exist an empty applicationcontext.
Both these fallback strategies tend to hide user errors. And
removing them will provide more clarity and also remove
a nuggest of complexity.
Types of changes
Checklist: