Multiple step definitions with spring context

This check

    public boolean addClass(final Class<?> stepClass) {
        if (!stepClasses.contains(stepClass)) {
            checkNoComponentAnnotations(stepClass);
            if (dependsOnSpringContext(stepClass)) {
                if (stepClassWithSpringContext != null) {
                    throw new CucumberException(String.format("" +
                        "Glue class %1$s and %2$s both attempt to configure the spring context. Please ensure only one " +
                        "glue class configures the spring context", stepClass, stepClassWithSpringContext));
                }
                stepClassWithSpringContext = stepClass;
            }
            stepClasses.add(stepClass);
        }
        return true;
    }

in SpringFactory actually prevents usage of multiple step definitions which have to use spring context.

[Ben1980]

I fixed it by doing the following…

A separate cucumber runner class:

@RunWith(Cucumber.class)
@CucumberOptions(
        plugin = { "pretty", "html:build/reports/cucumber" },
        glue = "com.whatever.feature.steps",
        features = "src/acceptance-test/resources/feature/"
)
public class AcceptanceTestsRunner {}

and a context loader class

@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT)
public class ContextLoader {
    @Before
    public void setUp() {
    }
}

Afterwards you can implement your step definitions and split them by their concerns. But make sure that ContextLoader is in the same package as the step definitions are, in my case com.whatever.feature.steps

[Ben1980]

Because it’s good programming style to keep responsibilities separated. Not only sourcecode but also tests should follow SRP.

E.g. a feature file for Login, another feature file for registration, another feature file for doing something meaningful. So we already separate the features into separate feature files, The same should be done with the step definition. Instead of having one huge step definition which handles all different features, it should be separated by it’s responsibility.