Getting Started
Welcome 👋. Learn how to get set up.
1. Create a project
Sign up to create a project. A project is a workspace for your targets (test jobs) and stores all of your test results data.
Learn more about how to structure your project.
2. Push data to your project from your automated tests
Add a small amount of code to your automated test framework. Libraries are available for popular languages and test frameworks:
That's it 🎉
Basic setup is complete. Complete advanced setup from the configuration menu, including:
- Add team members so your team can collaborate
- Add new targets so that you can consolidate results across a project
- Use the Tesults API in your CI/CD system to make pipeline gating and deployment decisions
- Flaky test detection, regression analysis, and failure explanations are surfaced automatically in the Tesults UI — if you need to access this intelligence outside the UI, such as in automated pipelines or AI agents, use the Insights API
- To query your test results in plain English from AI tools like Claude and Cursor, set up the Tesults MCP server
- Utilize task assignment for failing test cases
- Associate bugs to a test case so you can keep track of fixes required before a test can pass
- Look out for the flaky test indicator to identify tests that may have an issue or indicate a subtle bug with the app being tested
- See additional guides for advanced configuration
Manual tests
Most teams complement automated and programmatic tests with manual tests. For handling these test cases utilize test lists and runs.
Create a test list.
Test lists function as a source of truth for all of the test cases in your project or organization. Create or import test cases and store them permanently for reference and reuse across releases.
Create a test run.
Test runs are single use list of test cases that your team wants to run for a release. You can import test cases from your test lists, assign test cases to team members and track progress through to completion and then submit results.
Release records
Capture a permanent record of the test results associated with a release using release records.
Create a release record.
Release records let you attach automated and manual test runs to a release, capture approvals from team members, and seal the record once the release is complete. Use release records as an auditable history of what was tested and the outcomes for every release.
Release checklists
Consolidate automated and manual tests, along with any other tasks for release using a release checklist.
Create a release checklist.
Release checklists help keep track of all the tests and tasks that need to be completed for a release.
