Skip to main content

Overview

By integrating Test Management with GitHub, QA teams are now able to leverage the same collaboration features and project management tools as development teams.

  • Test instructions are captured using plain text markdown and managed in repositories following the same process as development (version control, pull requests, etc.).
  • No proprietary UI required for test authoring.
  • GitHub issue integration.
  • Test planning that leverages branches, issues, and GitHub Project Boards.
  • And support for automated fixturing using GitHub Actions and AWS Lambdas.

A Testspace manual project uses a Repository, Branches, Issues, and a Board all tightly integrated with GitHub.


To help you navigate Testspace, here is a brief description of terms and entities.

When you first sign up for Testspace, your Organization name becomes the subdomain of your Testspace URL - org-name.testspace.com.

The landing page for Testspace is an Organization's Projects Listing.

org-name.testspace.com
project-1
โ””โ”€ space-1
โ””โ”€ space-2
..
project-2
..

The Projects Listing is the results dashboard for the organization. A manual project is a collection of spaces that correspond to branches of the connected repository.

A Space representing the branch and is a collection of test Specs.

A Spec is a set of test Cases, as defined in a single specification file, and is a standalone executable unit.

organization
โ””โ”€ project
โ””โ”€ space
โ””โ”€ spec1
โ””โ”€ spec2
..

Specs can also optionally be organized into Cycles. A Cycle represents a collection (subset) of Specs typically used for planning different stages of test execution.

space
โ””โ”€ cycle
โ””โ”€ spec
..

Note that when reviewing the status of Spec using the Dashboard, it will be represented as a Suite the way as published automated test results.