Jenkins is a continuous-integration (CI) tool that helps deploy software projects, run automated tests while building a project, and monitor results. If you choose to, you can install and configure an automated testing tool, such as Cucumber, and a CI tool, such as Jenkins, to work with TM4J. This approach allows you to create BDD-Gherkin test cases. Once the test cases are approved, they can be exported manually, which generates a feature file parsable by Cucumber or pulled automatically from a Jenkins' build task.
Minimum System Requirement
Supported versions of Jenkins include 2.138.4 and above.
Automating the BDD workflow still requires the use of an external test automation tool which parses the standard BDD feature files and links it to an automated test code. You will need to implement the step definitions, which is the code that executes according to the sequence of steps defined in the feature files. Once the tests have been executed within the CI pipeline, the TM4J API, used, for example, by the Jenkins plugin post-build task, can send the test results back to Jira and publish them in the test cases.
Here’s a look at the basic workflow:
Want to give it a try? Check out Configuring Jenkins.