Cofactor is a single command with an exit code, so it works with whatever builds your software today. There is no plugin or special runner to set up.
Your pipeline gets a clear pass or fail, and your team gets a result they can read afterwards.
The command exits with zero when everything passed and one when something failed. A run that didn’t finish gets its own code, so it is never mistaken for a pass.
Results stream into the build log while the run is going, so you can see progress as it happens.
If the regression suite didn’t run, or only part of it ran, the gate fails. It only passes when the tests actually passed.
Cofactor posts one comment on the pull request and keeps it up to date. It shows the step that failed with the video next to it.
You can run a named suite, a set of tags, or everything, against the app and environment you choose.
The pipeline only needs the exit code. The report, video and trace are one link away for anyone who wants to look.
Playwright, Cypress and Selenium suites run on Cofactor too. Your existing tests get video, console and network capture added.
Which CI systems do you support?
Any of them. Cofactor is a command line tool with an API token, so if your pipeline can run a command, it can run Cofactor.
What does a failure look like in the log?
You see the failed tests by name, the counts, and a command to get the full explanation. The summary always matches the exit code.
Can it block a deploy?
Yes. The release gate runs your regression suite over the commits since the last release and exits non-zero on a failure, on a timeout, or if nothing ran at all.
Does it need access to my repository?
The pull request comment and the release gate need a GitHub app you install. Running a suite from your pipeline only needs an API token.
Join the waitlist, or book a call to talk through your release process.