Overview

Testspace is used for managing testing - both Manual and Automated. The section focuses on how to use the Testspace client to publish test results from an existing CI/automation environment.

$ testspace results.xml coverage.xml ...

• No Web API required
• Handles large volumes of content
• Handles output generated by industry tools (e.g. JUnit XML)
• Built-in support for code coverage and static analysis
• Custom Metrics support
• Works with CI matrix
• Can add additional information such as links to build machines, annotations including logs, etc.
• Can automatically organize your test result content based on your source directory structure

The Testspace client was designed to support large volumes of content

One of the purposes of Testspace is to manage the health of the software under test. Health can be assessed not only using test results, but also other metrics like code coverage, static analysis, and even custom metrics (i.e. timing, error logs, etc.).

---

When you first sign up for Testspace, you will choose an organization name, this becomes the subdomain of your Testspace URL.

my-organization.testspace.com

A Testspace organization is a collection of Projects.

A Project is a collection of Spaces.

A Space is a collection of test Suites and other content such as metrics, informational files, etc.

A Suite is a set of test cases.

organization
└─ project
   └─ space
      └─ suite

Spaces are the main vehicle for results analysis

The type of Testspace project - Connected or Standalone - determines how the Testspace client is used to publish data.

A Connected project is "connected" to a Repository. There is no management of Spaces, they automatically follow the branch workflow. Connected projects also seamlessly integrate with CIs. See the list of supported CIs here.

A Standalone project requires the management of Spaces.