Skip to main content

UI testing in continuous integration jobs

How to connect Gearset to different testing products for post deployment test runs.

Diogo Duarte avatar
Written by Diogo Duarte
Updated this week

UI testing plays a role in ensuring the reliability of your release process by helping to identify regressions introduced during deployments.

With Gearset, you can trigger UI tests across various third-party applications using our built-in integrations with select providers, or by leveraging outgoing webhooks for custom workflows.

Built-in integrations

Gearset includes built-in integrations with Accelq, Eggplant and Provar Manager for UI testing. Once they are configured, Gearset will automatically trigger the tests after each successful deployment.

Integrations through webhooks

It is also possible to trigger UI tests through the outgoing webhooks capability with dynamic variables, and there are specific guides available for GitHub, GitLab, Bitbucket and Azure DevOps (ADO).

Provar Testing

You can execute tests in Provar at the end of a CI run by setting up an integration with Provar Manager, or by triggering a custom Jenkins CI server job.

TestSigma

You can execute tests in TestSigma at the end of a CI run using their public REST API.

Tricentis Test Automation for Salesforce

You can execute tests in Tricentis Test Automation for Salesforce at the end of a CI run using their public REST API.

Publishing test results with third-party testing products

While Gearset's outgoing webhooks can execute tests, you can also integrate those results from your existing third-party testing products back into Gearset. This allows you to centralize the visibility of your testing efforts by sending and displaying results from external tools directly within the Gearset interface. Learn more about how to integrate Gearset with third-party testing products.

Did this answer your question?