How to Integrate Tosca with CI/CD for Continuous Testing in 2025

Introduction

In today's fast-paced software development environment, automation testing is no longer optional—it is a necessity. Businesses need to release high-quality software quickly, and manual testing cannot keep up with the speed of modern DevOps practices. This is where TOSCA Software Automation comes into play. As a leading automation tool, TOSCA enables teams to perform efficient, codeless testing. But to fully leverage its capabilities, integrating TOSCA with CI/CD pipelines is essential.

With continuous testing becoming a key practice in DevOps, organizations seek seamless automation integration to ensure rapid and reliable software delivery. This blog post provides a step-by-step guide to integrating TOSCA with CI/CD, helping you achieve end-to-end automation and continuous testing.

By the end of this article, you will learn:

Why CI/CD integration is crucial for test automation
How to integrate TOSCA with CI/CD tools like Jenkins, GitLab, and Azure DevOps
Best practices for implementing continuous testing with TOSCA
A hands-on tutorial for setting up TOSCA with Jenkins

Let’s dive in!



Why Integrate TOSCA with CI/CD?

1. Faster Release Cycles

CI/CD pipelines automate the software build, test, and deployment processes. When TOSCA Software Automation is integrated, test execution becomes part of the pipeline, ensuring immediate feedback on code quality.

2. Improved Test Coverage and Accuracy

TOSCA allows scriptless test automation, making it easier to create, maintain, and execute tests. By running automated tests in every CI/CD cycle, organizations achieve broader test coverage and detect issues early.

3. Reduced Manual Effort and Cost

Automating regression and functional tests within CI/CD significantly reduces manual testing efforts, leading to cost savings and higher efficiency.

4. Continuous Feedback and Faster Bug Fixes

When TOSCA is integrated into CI/CD, test results provide instant feedback. Developers can address defects immediately, improving software quality.

5. Supports Shift-Left Testing

Shift-left testing ensures defects are detected early in development. TOSCA’s integration with CI/CD enables frequent automated testing from the beginning of the development cycle.

Step-by-Step Guide to Integrating TOSCA with CI/CD

Prerequisites

Before integrating TOSCA Software Automation with a CI/CD pipeline, ensure you have the following:

✅ Installed TOSCA Commander and TOSCA Testsuite
✅ Installed TOSCA Distributed Execution (DEX) Server
✅ A CI/CD tool like Jenkins, GitLab, or Azure DevOps
✅ A version control system like Git
✅ Configured test cases in TOSCA

Now, let's explore how to integrate TOSCA with popular CI/CD tools.

TOSCA Integration with Jenkins

Jenkins is one of the most popular CI/CD tools used for automation. It allows teams to integrate TOSCA Tool for Testing into their workflows.

Step 1: Install Required Plugins

To enable TOSCA integration, install the Tricentis Tosca Plugin in Jenkins.

  1. Open Jenkins and navigate to Manage Jenkins > Manage Plugins
  2. Search for Tricentis Tosca and install the plugin
  3. Restart Jenkins after installation

Step 2: Configure Jenkins for TOSCA Execution

  1. Open Jenkins Dashboard and click on New Item

  2. Choose Freestyle Project and name it (e.g., "TOSCA_Test_Automation")

  3. Under Build Steps, select Execute Windows Batch Command

  4. Add the following command to trigger the TOSCA test execution:

    shell

    "C:\Program Files (x86)\TRICENTIS\Tosca Testsuite\ToscaCommander.exe" /run /project="C:\ToscaProjects\MyProject.tcs" /executionlist="RegressionSuite"
  5. Click Apply and Save

Step 3: Trigger TOSCA Tests in CI/CD Pipeline

  1. Commit changes to the repository (GitHub, GitLab, etc.)
  2. The Jenkins job automatically runs and triggers TOSCA test execution
  3. View the test results in Jenkins console output

TOSCA Integration with GitLab CI/CD

GitLab CI/CD provides a robust DevOps platform for automated testing. Follow these steps to integrate TOSCA Software Automation with GitLab.

Step 1: Define a GitLab CI/CD Pipeline

Create a .gitlab-ci.yml file in the repository:

yaml
stages: - test test_tosca: stage: test script: - 'C:\Program Files (x86)\TRICENTIS\Tosca Testsuite\ToscaCommander.exe /run /project="C:\ToscaProjects\MyProject.tcs" /executionlist="RegressionSuite"' only: - main

Step 2: Commit and Push the Changes

  1. Push the .gitlab-ci.yml file to your GitLab repository
  2. GitLab automatically triggers the pipeline and executes TOSCA tests

Step 3: View Test Execution Reports

  1. Navigate to CI/CD > Pipelines in GitLab
  2. Check test execution results and logs

TOSCA Integration with Azure DevOps

Step 1: Create a New Pipeline in Azure DevOps

  1. Navigate to Pipelines > New Pipeline
  2. Select your repository (GitHub, Azure Repos, etc.)
  3. Choose Starter Pipeline and edit the YAML file

Step 2: Define a TOSCA Execution Task

Add the following script to trigger TOSCA test execution:

yaml

trigger: - main pool: vmImage: 'windows-latest' steps: - script: | "C:\Program Files (x86)\TRICENTIS\Tosca Testsuite\ToscaCommander.exe" /run /project="C:\ToscaProjects\MyProject.tcs" /executionlist="RegressionSuite" displayName: 'Run Tosca Tests'

Step 3: Save and Run Pipeline

  1. Save the pipeline and run it
  2. View test execution results under Pipelines > Runs

Best Practices for Implementing Continuous Testing with TOSCA

1. Use Version Control for Test Cases

Store TOSCA test cases in Git to maintain version history and enable collaboration.

2. Implement Parallel Test Execution

Use TOSCA Distributed Execution (DEX) to run tests in parallel across multiple machines, improving execution speed.

3. Integrate with Reporting and Analytics Tools

Connect TOSCA with reporting dashboards like Power BI for real-time test insights.

4. Automate Test Data Management

Use TOSCA’s Test Data Service (TDS) to manage test data dynamically, ensuring reusability.

5. Schedule Automated Test Runs

Configure scheduled test executions in CI/CD to run nightly or during specific code changes.

Key Takeaways

🔹 Integrating TOSCA Software Automation with CI/CD enables continuous testing
🔹 Jenkins, GitLab, and Azure DevOps can automate TOSCA test execution
🔹 Following best practices improves automation efficiency and test coverage
🔹 CI/CD integration accelerates release cycles and enhances software quality

Conclusion

Integrating TOSCA Automation Tool with CI/CD ensures faster, more reliable software testing. By automating test execution within CI/CD pipelines, teams can improve efficiency and software quality. Now is the time to master TOSCA Software Automation and stay ahead in the world of DevOps.

🚀 Want to become an expert in TOSCA? Enroll in our TOSCA Training today

Comments

Popular posts from this blog