Cucumber in Web testing (part 8 of 8)

8. Keyword “Examples” and conclusion Gherkin keyword: Examples Cucumber provides another useful Gherkin keyword which is used scenario parametrization. A scenario with an “Example” keyword will be executed multiple times with different parameters. Here is an instance: Examples: Similar Posts from the author: Cucumber in Web testing (part 6 of 8) Cucumber in Web testing […]

Read more
Cucumber in Web testing (part 4 of 8)

4. TestRunner and Test steps To run features we need a Java class to start the test run. Here is a simple example: The TestRunner class needs to be annotated with @RunWith(Cucumber.class) and a body of it can be totally empty. By annotating the class with @CucumberOptions we can specify extra options to our test […]

Read more
Cucumber in Web testing (part 3 of 8)

3. Cucumber features “Feature” in cucumber is supposed to describe a single feature which is analog with “test group”/”test class” in standard Java world. A feature includes one or more scenarios. A scenario can be represented as a “test case” or a ”test method“ in standard Java world. The code of a cucumber feature need […]

Read more
Cucumber in Web testing (part 1 of 8)

1. What is cucumber Cucumber is a testing framework which supports behavior-driven development (BDD). BDD is principally an idea about how software development should be managed by both business interests and technical insight. Implementation of BDD starts with describing the test cases with English like sentences following up with the test case implementation. With this […]

Read more