You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 21, 2019. It is now read-only.
Kaare Nilsen suggested at the ROOTS conference that it should be possible to run scenarios as if they were JUnit tests. That would leverage existing tools like IDEs and build systems.
The idea:
@RunWith(CucumberJunit4Runner.class);
@Feature("features/jalla.feature") // optional - use convention if absent
public class JunitSpike {
@Test
public void mapsToScenario{};
}
These JUnit files could be generated
The text was updated successfully, but these errors were encountered:
The old JUnit code was deleted a while ago. We can dig it out from the past if we need it. Also worth studying: SpecFlow. Apparently they generate NUnit classes on the fly from features.
i needed such a junit runner for my current project, an already working version is here: https://github.com/eeichinger/utilities/tree/master/Cuke4DukeJUnit4Runner
note, that this is still in progress, but it shows how such a runner can be implemented as well as a full spring-test integration to support test transaction-rollback and di.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Kaare Nilsen suggested at the ROOTS conference that it should be possible to run scenarios as if they were JUnit tests. That would leverage existing tools like IDEs and build systems.
The idea:
These JUnit files could be generated
The text was updated successfully, but these errors were encountered: