From the course: Cucumber Essential Training

Continuous integration and BDD

From the course: Cucumber Essential Training

Start my 1-month free trial

Continuous integration and BDD

“

- [Narrator] Continuous integration and BDD. This is the high level work flow of how you could run your BDD tests with a continuous integration tool like Jenkins. You'd configure a job in Jenkins to point to your Java project's bomb dot xml file. This job is essentially a build definition that would be triggered manually on schedule. Or if changes are made to a source code repository. This job would invoke the Maven build tool to execute your build. The build process would produce compiled code and also produce BDD or any other configured test results as console output, and also as reports. You can reuse the pretty plugin report options to produce reports. Jenkins is just an example of a CI two. Other tools like circle CI can also implement the same workflow where you could run your BDD tests as a part of your build process. This is my Jenkins build configuration. When I look at the last build that was run, in the console output I can see that my results are there. And all three scenarios ran just fine. Just to summarize, you can use Jenkins or other CI tools to trigger builds. You can run Cucumber tests as a part of the build process, and produce test results as reports.

Contents