Run TestFlair tests from GitHub Actions
Connect a GitHub repository and TestFlair becomes a step in your pipeline: GitHub Actions starts a TestFlair test run, waits for the result and fails the build if the tests fail. Bugs found by TestFlair become GitHub issues.
Gate your builds on end-to-end tests
- Generate a CI token in TestFlair and store it as the TESTFLAIR_CI_TOKEN Actions secret.
- Copy the workflow 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, so you can read what broke without opening TestFlair.
Push bugs to GitHub issues
Map a TestFlair project to a repository and push its bugs as GitHub issues in one action. Sync history shows each push with its synced and failed counts.
Dispatch workflows from TestFlair
The same page can dispatch a GitHub Actions workflow on the mapped repository.
Frequently asked questions
How does TestFlair connect to GitHub?
With OAuth for GitHub.com, or with a personal access token, which also works for self-managed instances. One connection serves every project in the workspace.
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 workflow snippet stays the same.