I obviously made a mistake when I wanted to build the example in small steps. I had prepared an intermediate step that actually wasn’t compiled with the blog post. The other steps has been compiled when I built the blog post. I forgot to update this intermediate step when I updated to a newer version of Cucumber.

The import should be

cucumber.api.java.en.Given;

etc. as it is later in the text.

I am glad that you spotted the error.

Thanks!
Thomas

I have tried to execute the example you propose in your post, but there seems to be an error.
I have created the files included in this post, but when I execute
$ mvn test
I get the following error:
[ERROR] /home/my_name/dev/tests/cucumber-primer/model/src/test/java/se/waymark/rentit/steps/RentStepdefs.java:[6,29] error: package cucumber.annotation.en does not exist

In your pom.xml you use cucumber-java 1.1.1, as it says:
cucumber-java
1.1.1
But version 1.1.1 of cucumber-java des not contain cucumber.annotation.en

The missing package exists in cucumber-java 1.0.1 (according to http://grepcode.com/file/repo1.maven.org/maven2/info.cukes/cucumber-java/1.0.1/cucumber/annotation/en/Given.java?av=f)

So I think you mixed two versions of the example in the post, including a pom.xml that is newer than the .java. I have tried to use 1.0.1, 1.0.2, 1.0.7, … of the dependencies, but then a different error appears.
Could you please correct me if I’m wrong or specify the right version of modules?

Thank you.

TestWatcher is abstract, at least in JUnit 4.10. Implement your own rule that extends TestWatcher instead. I implement a simple example in the class SimpleOnFailed.

HTH
Thomas

@Rule
public TestWatcher testWatchThis = new TestWatcher() {
@Override
protected void failed(Throwable e, Description description) {
LOG.error(“Only executed when a test fails”);
}
};

within a test class, I always get an Exception complaining that “Field testWatchThis must implement MethodRule”.

What’s the deal with that? I’m using JUnit v4.11.

The folder structure is critical. The reason is that I use Maven to build and execute the project.
Maven is about convention over configuration. The convention is that all source code should live in the directory src. The production code should live in main and test code should live in test. Any Java code should live in java. If you organize you Java code in packages, then will the Java directory be the package root and you need to add the proper directories in the Java directory to reflect your packages.

HTH
Thomas

I would probably implement it with the ant plugin today if I did it again.

I am glad if it helped you!
Thomas

Thomas