Many teams set up their continuous integration (CI) server to run Cucumber every time someone shares changes with the rest of the team. Since it’s a command-line tool, there is nothing fancy you need to do—just plop the cucumber command into the CI project’s configuration.
You may want to use slightly different command-line options for CI than you use on your own workstation. You can do this by defining a special profile for the CI build (for example ci).
It’s common to have missing or pending steps while we’re working on a new scenario. Some teams strive to keep the mainline (trunk) of the source repository pristine, without any pending or missing steps.
CI systems detect failure ...