Developer Guide

General concepts

1. A module is a set of distinct features like cart, gallery etc.
2. Features under cart module could be checkout, addtowishlist etc.
3. Each feature can have scenarios. e.g. Checkout single product, Checkout multiple products
4. Each module would have its own sub folder and subpackage.
5. All feature files will reside under its module.
6. All test classes (step definitions) reside under sub package for that module.
7. All test classes will be named as <Featurename>Test.java
8. Each scenario can have one or more tags. Typically tags include module, feature, test-type, test-priority
9. e.g. @cart @checkout @singleproduct @smoke @medium
10. Tags can also be given at feature file level (typically module and feature level tags)

Source code organization

Source tree of the project looks like below -

• data - Contains classes that represent test data
• page - Contains POM classes (page object model) ** This can have sub packages based on modules
• utils - Contains utility classes
• runner - Contains Cucumber runner class - refer RunnerCourgette.java for more details
• stepdefinition - Contains cucumber step definition classes (aka glue) ** This can have sub packages based on modules