Test every deployment
Connect
SPIRITT
BugBugBugBug
Tests that run themselves
SPIRITT makes your BugBug tests part of how you ship. It runs them after deploys and on schedule, reads every run's results and turns failures into issues, alerts and clear go or no-go calls.
What you can do with BugBug.
Tests on every deploy
New deployments trigger the right BugBug tests with the right profile automatically.
Failures become fixes
Failed runs turn into issues with the error, browser and timing attached.
Quality you can see
Suites, tests and run history roll into reports on stability and flakiness.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for the testing and release work you want automated.
02
Connect BugBug
Connect BugBug with your API key so SPIRITT can list tests and suites and run them.
03
Delegate an outcome
Tell SPIRITT when tests should run and who needs results. It wires it up and keeps watch.
Hand over a mission.
Choose a mission. Make it yours.
Put BugBug to work.
Ship with every test green.
Questions
BugBug, with SPIRITT.
01What can SPIRITT do with BugBug?+
List your tests and suites, run tests with a chosen profile and variable overrides, and read detailed run history with status, timing and errors.
02How do I connect BugBug?+
Connect it with your BugBug API key.
03What starts a test run?+
A schedule, a new deployment, a pull request or a ticket status change that SPIRITT is watching in your other apps.
04Can I change settings per run?+
Yes. Each run can use a different profile and override variables such as URLs or test accounts.
05Can SPIRITT spot flaky tests?+
Yes. It reads run history, finds tests that flip between pass and fail and ranks them for stabilizing.
06Where do results go?+
Slack, GitHub, Linear, Jira, PagerDuty or a dashboard SPIRITT builds for you.