Run TestFlair tests from GitLab CI
Connect a GitLab project and TestFlair becomes a stage in your pipeline: GitLab CI starts a TestFlair test run, waits for the result and fails the pipeline if the tests fail. Bugs found by TestFlair become GitLab issues.
Gate your pipeline on end-to-end tests
- Generate a CI token in TestFlair and store it as a masked TESTFLAIR_CI_TOKEN CI/CD variable.
- Copy the pipeline snippet TestFlair builds for the test runs you pick.
- The job starts the runs, polls until they finish and exits non-zero if a run failed.
- A failed job log lists each failed case with its actual error.
Push bugs to GitLab issues
Map a TestFlair project to a GitLab project and push its bugs as GitLab issues in one action. Sync history shows each push with its synced and failed counts.
Trigger pipelines from TestFlair
Enter a branch or ref and trigger a GitLab pipeline on the mapped project from TestFlair.
Frequently asked questions
Does TestFlair work with self-managed GitLab?
Yes. Connect GitLab.com with OAuth, or connect any instance — hosted or self-managed — with its base URL and a personal access token.
What runs when the pipeline calls TestFlair?
The test cases, engine and execution preferences saved in each selected TestFlair test run. To change what CI runs, edit the test run in TestFlair; the pipeline snippet stays the same.