Blog
How to run UI tests from GitHub Actions, GitLab CI or Jenkins
To run UI tests from CI, add one step that starts the test run on your test platform, waits for the result, publishes a JUnit report and fails the build when a test fails. SmartestQA gives you that step ready-made for GitHub Actions, GitLab CI, Jenkins and Azure Pipelines.
The problem
UI tests that run only at night find a broken deploy the next morning. Tests that run inside the CI job need browsers, drivers and a runner that can reach the application, and they make every build slow.
The practical middle is to let CI start the run and wait for it, while the tests themselves run where they already run well.
How SmartestQA does it
The CI job only asks and waits. The run is a normal SmartestQA run, with its report and its notifications.
- One step in your pipeline. It starts the run, waits, and returns pass or fail.
- Results where developers look. A JUnit report in the merge request or the build.
- No special runner. The tests run on SmartestQA servers or on your own machine inside your network.
- One suite, several environments. Pass the environment as a parameter.
Questions and answers
Should UI tests block the build?
Block on a small, stable suite and report on the rest. A smoke run of a few minutes is a fair gate; a full regression is better started after the deploy.
Do I need a self-hosted runner?
No. The CI job only sends requests and waits, so a hosted runner is enough.
Which CI tools are supported?
GitHub Actions, GitLab CI, Jenkins, Azure Pipelines and plain shell.
Where to read more
See How do I build, run and schedule a regression suite?, or the documentation: CI/CD.

