Skip to content
This repository has been archived by the owner on May 21, 2019. It is now read-only.

Run with JUnit #3

Open
aslakhellesoy opened this issue May 7, 2009 · 4 comments
Open

Run with JUnit #3

aslakhellesoy opened this issue May 7, 2009 · 4 comments

Comments

@aslakhellesoy
Copy link
Contributor

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

@torbjornvatn
Copy link
Contributor

Should the JUnit code be moved into its own branch until someone fixes it?
"Don't live with broken windows"

@aslakhellesoy
Copy link
Contributor Author

The JUnit code is not a broken window - it's a deserted town ;-)

Go ahead and move it all to a junit branch so we can have cleanliness on master if you want.

@aslakhellesoy
Copy link
Contributor Author

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.

@eeichinger
Copy link

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants