Saturday, 13 September 2025

Tosca with Jenkins Integration.

Integrating Jenkins with Tricentis Tosca is a practical step for teams looking to bring more automation testing and consistency into their CI/CD pipelines. This setup allows you to execute Tosca test cases automatically from Jenkins, helping ensure smoother, more reliable test cycles with less manual intervention. below are the steps for setting up the Tosca Jenkins Integration using the Tricentis CI Plugin and ToscaCIClient.

Prerequisites for integration:

To connect Jenkins with Tricentis Tosca successfully, organizations need to have certain tools and conditions ready. First, you must have the Jenkins plugin for Tricentis Tosca. This plugin helps link the automation features of both systems. Make sure the plugin works well with your version of Jenkins because updates might change how it performs.

Next, it is important to have a set up Tricentis test automation environment. This is necessary for running functional and regression tests correctly within the pipeline. Check that the Tosca Execution Client is installed and matches your CI requirements. For the best results, your Tosca Server should also be current and operational.

Finally, prepare your GitHub repository for configuration. This allows Jenkins to access the code, run test cases, and share results smoothly. With these steps completed, organizations can build effective workflows that improve testing results and development efforts.

Step-by-step guide to configuring Tosca in Jenkins

Achieving the integration requires systematic configuration of Tosca within Jenkins. Below is a simple guide:

Step 1: Install Jenkins Plugin – Tricentis Continuous Integration

1. Go to Jenkins Dashboard → Manage Jenkins → Manage Plugins.

2. Search for Tricentis Continuous Integration in the Available tab.

Tosca Jenkins Integration Install Jenkins Plugin

3. Install the plugin and restart Jenkins if prompted.

Step 2: Configure Jenkins Job with Tricentis Continuous Integration

Once you’ve installed the plugin, follow these steps to add it to your Jenkins job:

  • Go to your Jenkins job or create a new Freestyle project.
  • Click on Configure.
  • Scroll to Build Steps section.
  • Click Add build step → Select Tricentis Continuous Integration from the dropdown.

Configure Jenkins Job with Tricentis Continuous Integration

Configure the Plugin Parameters

Once the plugin is installed, configure the Build Step in your Jenkins job using the following fields:

S. NoField NamePipeline PropertyRequiredDescription
1Tricentis client pathtricentisClientPathYesPath to ToscaCIClient.exe or ToscaCIJavaClient.jar.
If using .jar, make sure JRE 1.7+ is installed and JAVA_HOME is set on Jenkins agent.
2EndpointendpointYesWebservice URL that triggers execution.
Remote: http://servername:8732/TOSCARemoteExecutionService/
DEX: http://servername:8732/DistributionServerService/ManagerService.svc
3TestEventstestEventsOptionalOnly for Distributed Execution. Enter TestEvents (names or system IDs) separated by semicolons.
Leave the Configuration File empty if using this.
4Configuration fileconfigurationFilePathOptionalPath to a .xml test configuration file (for detailed execution setup).
Leave TestEvents empty if using this.

Step 3: Create a Tosca Agent (Tosca Server)

Create an Agent (from Tosca Server)

You can open the DEX Monitor in one of the following ways:

  • In your browser, by entering the address http://:/Monitor/.
    Directly from Tosca Commander.
  • To do so, right-click a TestEvent and select one of the following context menu entries:
    Open Event View takes you to the TestEvents overview page.
    Open Agent View takes you to the Agents overview page.

Navigate the DEX Monitor

The menu bar on the left side of the screen allows you to switch between views:

  • The Agent View, where you can monitor, recover, configure, and restart your Agents.
  • The Event View, where you can monitor and cancel the execution of your TestEvents.

Enter:

  • Agent Name (e.g., Agent2)
  • Assign a Machine Name

This agent will be responsible for running your test event.

Tosca Jenkins Integration

Step 4: Create and Configure a TestEvent (Tosca Commander)

  • Open Tosca Commander
  • Navigate to: Project > Execution > TestEvents
  • Click Create TestEvent
  • Provide a name like Sample
  • Step 4.1: Assign Required ExecutionList
    • Select the ExecutionList (this is where you define which test cases will run)
    • Select an Execution Configuration
    • Assign the Agent created in Step 3
  • Step 4.2: Save and Copy Node Path
    • Save the TestEvent

      Tosca Jenkins Integration

    • TestEvent → Copy Node Path

      TestEvent → Copy Node Path

    • Paste this into the TestEvents field in Jenkins build step

      Paste this into the TestEvents field in Jenkins build step

Step 5: How the Integration Works

Execution Flow:

  • Jenkins triggers test execution using ToscaCIClient.
  • The request reaches the Tosca Distribution Server (ManagerService).
  • Tosca Server coordinates with AOS to retrieve test data from the Common Repository.
  • The execution task is distributed to a DEX Agent.
  • DEX Agent runs the test cases and sends the results back.
  • Jenkins build is updated with the execution status (Success/Failure).

Tosca Jenkins Integration

Step 6: Triggering Execution via Jenkins

Once you’ve entered all required fields:

  • Save the Jenkins job
  • Click Build Now in Jenkins

What Happens Next:

  • The configured DEX Agent will be triggered.
  • You’ll see a progress bar and test status directly in the DEX Monitor.

    Triggering Execution via Jenkins

  • Upon completion, the Jenkins build status (Pass or failure) reflects the outcome of the test execution.

    Tosca Jenkins Integration

Step 7: View Test Reports in Jenkins

To visualize test results:

  • Go to Manage Jenkins > Manage Plugins > Available
  • Search and install Test Results Analyzer
  • Once installed, configure Jenkins to collect results (e.g., via JUnit or custom publisher if using Tosca XML outputs)
Notes: 

Why should I integrate Tosca with Jenkins?

Integrating Tosca with Jenkins enables continuous testing, reduces manual effort, and ensures faster, more reliable software delivery.


Can I use Tosca Distributed Execution (DEX) with Jenkins?


Yes, Jenkins supports both Remote Execution and Distributed Execution (DEX) using the ToscaCIClient.


Do I need to install a plugin for Tosca Jenkins Integration?


Yes, you need to install the Tricentis Continuous Integration plugin from the Jenkins Plugin Manager to enable integration.


What types of test cases can be executed via Jenkins?


You can execute any automated Tosca test cases, including UI, API, and end-to-end tests, configured in Tosca Commander.


Is Tosca Jenkins Integration suitable for Agile and DevOps teams?


Absolutely. This integration supports Agile and DevOps practices by enabling faster feedback and automated testing in every build cycle.


How do I view Tosca test results in Jenkins?


Install the Test Results Analyzer plugin or configure Jenkins to read Tosca’s test output via JUnit or a custom result publisher.

Saturday, 6 September 2025

What is an AI Co-Pilot?

An AI Co-Pilot is an artificial intelligence assistant designed to help users perform tasks more efficiently by providing contextual suggestions, automating repetitive actions, and enhancing productivity within existing workflows. It typically works alongside users, offering real-time support without taking independent action.

However, more recently, AI Agents or Agentic AI have arrived as the new kid on the block who seems to be drawing all the limelight (and for good reason!).

What is Agentic AI?  

Agentic AI refers to autonomous AI systems capable of not only assisting users but also acting independently to complete multi-step goals without constant human intervention. These systems leverage advanced automation, conversational interfaces, and decision-making capabilities to deliver end-to-end task execution.

Tosca is evolving with AI!

Tricentis has introduced Agentic AI into Tosca, taking automation to the next level.

While Tosca Copilot acts as an assistive AI—helping with queries, test summaries, and troubleshooting—Agentic AI goes further by autonomously creating, adapting, and executing tests from natural language.

Key Highlights:

Copilot = Assistive AI → boosts usability & guidance

Agentic AI = Autonomous AI → drives end-to-end test automation

Reported 85% faster test creation & 60% productivity gains

This marks a big shift in how QA teams can leverage AI to accelerate testing and improve software delivery.