Skip to main content

Tutorial Setup

This tutorial gets new Testspace users up to speed quickly, using a Standalone project — no repository connection required. If your team wants specs and automation living in git instead, see Using a Connected Repo once you've finished here; everything you learn in this tutorial still applies.

There are two steps required for setup:

  1. Sign up for a Testspace account, if you don't already have one
  2. Create a project and space to use for this tutorial

Sign up​

If you don't already have a Testspace account, go to testspace.com/pricing and choose Sign up with Email — no GitHub, GitLab, or Bitbucket account is required for this tutorial. (You can also sign up with one of those providers if you prefer; see Sign up for the full set of options.) See the pricing page for plan details.

Create a Project​

To create a Testspace project click on the "New Project" button at the top right of the Testspace landing page, and select STANDALONE.

New Standalone Project

Provide a Project name (e.g. tutorial) and SUBMIT.

New Space​

Once the project exists, click New Space to create a space to work in.

New Space

Provide a Space name (e.g. main) and check Enable Manual Testing — this tutorial covers both publishing and manual testing, and Manual Testing needs to be turned on per space.

Terms​

The following are some terms used throughout this tutorial.

  • project - A top-level container for one or more spaces.
  • space - An environment for tracking results — for a Standalone project, created and managed directly; for a Connected project, mapped automatically to a repo branch.
  • spec - A set of test instructions represented by a single markdown file. Aka test spec.
  • suite - Contains testing status, made up of one or more test cases.

Recap​

At this point, a new Standalone Testspace project and space have been created — ready to use for publishing test results and executing manual tests, no repository required.

A Testspace project can be used for publishing test automation results, implementing and executing manual tests, and conducting exploratory testing.

Let's start doing things.