| Recipe 10 | Add Cucumber to Your Continuous Integration Server |
Problem
You want to run your Cucumber tests automatically on a shared machine every time someone on your team checks in a change.
Ingredients
-
Jenkins, the open source continuous integration server[64]
-
The Git version control system[65]
-
Jenkins plug-ins for Git and Rake (installed using the admin tools)
-
A post-commit hook[66] for notifying Jenkins that your source code has changed
-
cURL[67] for interacting with Jenkins from command-line scripts
Solution
In Recipe 9, Run Your Features Automatically with Guard and Growl, we saw how the Guard library can watch the files on an individual developer’s machine and rerun Cucumber tests whenever the source code changes. A continuous ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access