Tosca CI Integration with Jenkins: A Guide

If you're working in software development, you know that Continuous Integration (CI) is a game-changer. It ensures that your codebase remains stable and that issues are caught early. Integrating Tricentis Tosca with Jenkins can streamline your testing process, making it easier to maintain high-quality software. Here’s a simple guide to help you set up Tosca CI integration with Jenkins.

Step 1: Prerequisites

Before you start, make sure you have:

Jenkins Installed: Ensure Jenkins is installed and running. You can download it from the official Jenkins website.

Tosca Installed: You should have Tricentis Tosca installed and configured on your system.

Tosca CI Client: The Tosca CI Client should be installed on the machine where Jenkins is running.

Step 2: Configure Tosca for CI

Create Test Cases in Tosca: Develop and organize your test cases in Tosca.

Set Up Execution Lists: Create execution lists that group your test cases in a logical order. These lists will be triggered during the CI process.

Step 3: Install Jenkins Plugins

Tosca CI Plugin: You need to install the Tosca CI Plugin in Jenkins. Go to Manage Jenkins > Manage Plugins > Available and search for "Tosca". Install the plugin and restart Jenkins if required.

Required Plugins: Ensure you have other necessary plugins installed, like the "Pipeline" plugin for creating Jenkins pipelines.

Step 4: Configure Jenkins Job

Create a New Job: In Jenkins, create a new job by selecting New Item, then choose Freestyle project or Pipeline depending on your setup.

Configure Source Code Management: If your test cases or project are in a version control system (like Git), configure the repository URL and credentials under the Source Code Management section.

Build Steps: Add build steps to integrate Tosca tests.

For a Freestyle project, add a Build Step and select Execute Windows batch command or Execute shell script.

Use the Tosca CI Client command to trigger the execution list: sh ToscaCIClient.exe --executionList="" --project=""

Step 5: Configure Pipeline (Optional)

If you prefer using Jenkins Pipelines, you can add a Jenkinsfile to your repository with the following content:pipeline { agent any stages { stage('Checkout') { steps { git 'https://github.com/your-repo/your-project.git' } } stage('Execute Tosca Tests') { steps { bat 'ToscaCIClient.exe --executionList="<Your Execution List>" --project="<Path to Your Tosca Project>"' } } } }

Step 6: Trigger the Job

Manual Trigger: You can manually trigger the job by clicking Build Now in Jenkins.

Automated Trigger: Set up triggers like SCM polling or webhook triggers to automate the process.

Step 7: Review Results

Once the build completes, review the test results. The Tosca CI Client will generate reports that you can view in Jenkins. Check the console output for detailed logs and any potential issues.

Conclusion