Winter

Winter is a set of predefined Cucumber Step Definitions interacting with Spring-Automocker available mocks.

Getting started

Alter your Maven pom.xml with the following:

<project>
...
	<build>
		<plugins>
			<plugin>
				<groupId>com.github.ledoyen.winter</groupId>
				<artifactId>winter-maven-plugin</artifactId>
				<version>${winter.version}</version>
				<executions>
					<execution>
						<goals><goal>test</goal></goals>
					</execution>
				</executions>
			</plugin>
		</plugins>
	</build>
</project>

And add some feature files. For example:

@txn
Feature: Owner service

Scenario: owner creation
  When using an HTTP header Content-Type=application/json
  And an HTTP POST request is made on resource /owner with content
    """
      {
      	"firstName": "Steeve",
      	"lastName": "Jobs",
      	"address": "1 Infinite Loop",
      	"city": "Cupertino",
      	"telephone": "0123456789"
      }
    """
  Then the HTTP response code should be CREATED
  And an HTTP GET request on resource /owner/list should respond status 200 with body matching
  | Expression                             | Expected result |
  | $[?(@.firstName == 'Steeve')].lastName | Jobs            |
  | $[?(@.firstName == 'Steeve')].city     | Cupertino       |

Feature files are looked for in the features test directory (src/test/resources/features). To override that behavior, use Cucumber options through systemPropertyVariables parameter.

Entry class is the only main class available (execution will fail otherwise). To override that behavior, use configurationClass parameter or winter.configurationClass System property.

Cucumber concerns

As Winter is now based on Cucumber, Cucumber-related features and limitations are present.

Cucumber options

You can use Cucumber options to customize your test structure and add custom Step Definitions. Step Definitions supports Spring's annotation such as Autowired without any additional @ContextConfiguration if you use WinterTestLauncher.

Cucumber runner

This applies only if you are not using WinterTestLauncher or WinterJUnit4FeatureRunner, but Cucumber instead. By default Cucumber does not work well with multiple ObjectFactory available in root package cucumber.runtime. So dependencies like cucumber-spring or cucumber-guice will not cohabite nicely with Winter.

To fix the problem you have two choises :

• Dedicate specific classpaths for specific executions through your build system
• Force cucumber to use one or another ObjectFactory by passing the adequate system property:

-Dcucumber.api.java.ObjectFactory=cucumber.runtime.winter.WinterObjectFactory

If you do not have another ObjectFactory in your classpath, Cucumber will nicely pickup the Winter one through its cucumber.runtime.java.ObjectFactoryLoader.

To benefit from Winter prefefined Step Definitions you will also have to indicate gluecode location:

@RunWith(Cucumber.class)
@CucumberOptions(glue = { "classpath:com/github/ledoyen/winter/stepdef", "classpath:my/custom/stepdef" })
public class MyApplicationCucumberTest {

}