Getting Started
Three steps take you from a new account to your first Results. Each step links to the Tutorial, which walks through it with sample content, and to the reference pages. Concepts explains the words used here.
1. Sign Up
Sign up with Email, GitHub, Bitbucket or GitLab. You choose your Organization's subdomain, which becomes your Testspace address: your-organization.testspace.com. See Sign Up.
2. Create a Project
On your Organization's Projects tab, click New Project at the top right. There are two types of Project:
- Standalone: you create its Spaces and choose its settings in Testspace, and write Manual specs in Testspace's editor. When your Organization has no GitHub, GitLab or Bitbucket service connected (as after signing up with Email), New Project opens the Standalone form directly. Tutorial: Setup. Reference: Standalone Projects.
- Connected: the Project follows a repository, with a Space for each branch and pull request, and Manual specs kept in the repository. It needs the Organization connected to GitHub, GitLab or Bitbucket (Integrations). New Project then lists your repositories, with a STANDALONE button at the dialog's bottom left for a Standalone Project. Quick start: Connected Projects.
It needs no repository, and it publishes automated results the same way a Connected Project does. You can add a Connected Project later; a Standalone Project doesn't convert, so you'd create the Connected one alongside it.
3. Publish Results or Run a Manual Spec
Results go into a Space of your Project, and both kinds show in the same views.
- Publish automated results: install the Testspace client and push your test results file with one command, by hand or from any CI system. Tutorial: Publish Results, or the Connected quick start for CI. Reference: Publish and CI/CD Support.
- Write and run a Manual spec: in a Standalone Project, create a Space with Enable Manual Testing checked, click New Spec on its Manual tab, then open the spec and click START. Tutorial: Write & Run a Spec, or the Connected quick start for specs in a repository. Reference: Manual Testing.
Then see what your Results show: Review Results walks through the Current, Failures and Results tabs and a Result's Health, and Health and Failures explain the rules. Next Steps lists what to explore after that.