Introduction
Testspace is test management for automated, manual and exploratory testing. It collects every test result for your product in one place and tracks its health over time.
How Results Get In
Automated tests publish their results with the Testspace client: one command, from any CI system or by hand. Results from parallel jobs are aggregated, and for a Connected Project each branch and pull request gets its own Space automatically.
testspace path/to/**/results*.xml coverage.xml
Manual tests are specs written in Markdown, either in Testspace's editor or in a connected GitHub, GitLab or Bitbucket repository. Testers run them, ad hoc or in test sessions, and record a status, issues and observations for each case.
# Login
Check that a user can sign in.
## Valid password
- Enter a valid user name and password
- Click Sign in
One View of Both
Automated and manual results appear in the same views:
- Results: each Result's Suites and cases, with views for failures, issues and the slowest tests, plus each case's history across Results.
- Health: every Result is Healthy or Unhealthy against the checks you set, shown in listings and in the check Testspace posts on your commits.
- Failure Tracking: each failing case is tracked from Result to Result as New, Flaky or Consistent, until it really passes again.
- Metrics and Insights: code coverage, static analysis and custom metrics with graphs, and Insights across a Project's Spaces.
- Issues: link failures to Jira, GitHub, GitLab or Bitbucket issues, or create issues from them, and see when an issue is closed but its tests still fail.
Where to Start
- Concepts: Organizations, Projects, Spaces and Results, and the words Testspace uses.
- Getting Started: sign up, create a Project, and publish or run your first tests.
- The Tutorial, step by step.
- Live demos: published results and Manual testing, to explore without an account.
For more, see Publish Overview and Manual Overview.