CI in 5 minutes flat

Prerequisites

Before getting started, make sure you have the following:

• CucumberStudio account
• GitHub account
• Travis CI account
• Test execution computer setup
• Text editor
• git installation
• hiptest-publisher installation

System Under Test

The tutorial tests an automated espresso machine using code. The project follows Behavior Driven Development standards with features as folders, Gherkin syntax, and declarative scenarios.

Step One – Getting the Project

Login to CucumberStudio and access your projects list. Select Example projects and choose the Coffee machine sample. Fork the "CucumberStudio publisher samples" GitHub repository, selecting your preferred language/framework combination.

Step Two – Configuration

Copy the secret token from Project Settings' "Test code generation" section. Add the token to your configuration file. Then run:

hiptest-publisher -c <path to config file> --actionwords-signature

Update test files with:

hiptest-publisher -c <path to config file> --without=actionwords

Step Three – Running Tests Locally

Execute tests using framework-specific commands. For example, with Python/UnitTest:

python bootstrap.py
bin/buildout
bin/test --with-xunit

Step Four – Setting Up CI

1. Activate Travis CI for your forked repository.
2. Copy the test run ID from CucumberStudio's Test runs section.
3. Modify the .travis.yml file, replacing the test run ID and removing --token=$SECRET_TOKEN.
4. Push changes to GitHub.
5. Update the README.md build badge.

Wrap Up

Integrating CucumberStudio with CI is a pretty fast operation once your actionwords are implemented. Your team now has a full BDD pipeline — from writing scenarios in CucumberStudio to running automated tests on every push.

Try CucumberStudio and set up your CI pipeline today.