User Tools


2-page overview Testspace Overview

Testspace is a Quality Analytics system for test automation workflow. Testspace turns test content such as test results, code coverage, static analysis, logs, and source code changes into actionable metrics. Testspace's built-in analytics based indicators enable data-driven decision making concerning the state of quality for software projects.

A simple command line utility called the Testspace client is used to push content (files) to the Testspace server.

$ testspace tests*.xml code-coverage.xml ...

Enterprise users read this article

The first thing is to Sign Up and create an Organization. An Organization is simply a collection of Projects. A Project contains a collection of Spaces. A Space is a container for results published from aggregating and analyzing pushed test content and maintaining historical records used for Insights.

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

The main purpose of Testspace is to provide published test content for the team. To create this content requires an Organization, Project, Space, and Credentials. The following is a longhand version of a command line statement for using the Testspace client. The test content files (i.e. tests*.xml) is your stuff!

$ testspace tests*.xml

Where to Start?

Read the Push Data article

To get started a "general understanding" of Testspace and where to access important information going forward is recommended . For example, what types of data can be pushed to the server? Without data to push there is nothing to do. Related to types of data supported, what format is required? Many tools have options that Testspace requires (i.e. JUnit test output). We also provide details on adding Testspace to your automation workflow. To help provide understanding and context we recommend reviewing two simple examples – our version of hello world.

The following steps are presented to acquire a general understanding of Testspace:

  1. Read the How To Push Data article. This article list the types of data (lots), formats, methods, etc.
  2. Understand the two Project types: Standalone and Connected. If you are using GitHub or Bitbucket Connected Projects might be the primary type of project to use.
  3. Checkout our 2 simple examples: Desktop Example and GitHub CI Example. Both examples walk you through creating a project and doing stuff.
  4. Read the How To Add To CI article. The mechanics of adding our client to your existing automation process.
  5. Review the frameworks & tools articles. This is a collection of articles detailing how to convert existing tools to produce compliant format for pushing.

This Getting Started set of articles will guide you through the simple steps of creating a Project and pushing sample data to a Space. Once you are setup and familiar with Testspace, and have some example content published, go ahead and invite other Users to join your Testspace Organization.

The following sections provide a brief overview of the hierarchy of Testspace.


A Testspace Organization is a named collection of Projects. You navigate to your Organization by pointing a web browser to Testspace presents information in views that correspond to the hierarchical levels of Projects and Spaces. You navigate between pages by clicking links.

By default, the Projects tab is selected. This view gives you a comprehensive look at the current state of all Projects and Spaces within the Organization1). Testspace has two distinct types of Projects, Standalone, and Connected, to support differences in testing focus – Unit, Integration, and System – and their associated workflows.

The Organization view comprises the following tabs:

  • Projects displays a list of Projects and child Spaces associated with the Organization (selected by default)
  • Users displays a list of users that have access to the Organization (Organization members with Admin/Owner privilege)
  • Activity displays a journal of all Organization events sorted by date and time (Organization members)
  • Account displays settings and subscription plan (Account owner only)


To access a Project from the Organization view, select the Projects tab, then click on the name of the desired Project. Recall that a Project is a collection of similarly focused Spaces. Each Project also hosts Notes for annotating specific result sets, hosting discussions, and assigning/tracking to-do items.

The Project view comprises the following tabs, which are used to select a page within the view:

  • Spaces - List of Spaces belonging to the Project (tab selected by default)
  • Insights - Summary of results and metrics for member Spaces
  • Results - List of recently published results for all child Spaces
  • Notes - List of discussions and to-dos items associated with the Project
  • Activity - Journal of all events related to this Project sorted by date and time


You can access a Space from either the Organization or Project views. In either case, click on the name of the desired Space to access it's view page. A Space typically represents a set of results related to a specific software package, software branch, unique application, etc.

The Space view comprises the following tabs, which are used to select a page within the view:

  • Schema - Hierarchical design of the Space's tests with the most recent results are overlaid
  • Metrics - Graphs showing metrics for the space
  • Results - List of previously published results
  • Activity - Journal of all events related to this Space sorted by date and time

What's Next?

For more details refer to our product blog at

1) Hidden Spaces are not shown in this view.

Page Tools