User Tools

Desktop Example

Using Open Organization? If yes go to the GitHub CI Example.

This Desktop Example walks through the following steps:

  1. Create a Testspace Project and Space
  2. Download and configure the Testspace Client
  3. Push some example test content files to the Testspace Server

Example published results can be viewed Here.

New Project

After completing the new account process – and every time you log in thereafter – you'll land on the Projects tab, the home view for your Testspace Organization.

On first time access, your Projects page will display the following.

Select the New Project button to bring up the dialog shown below.

Provide a Project name and optional description - notification settings can be changed at any time.

Select SUBMIT, and then select the project-name-link for your new project to go to the Spaces tab which should look as follows.

Select the New Space button to bring up the dialog shown below.

Provide a Space name and optional description and SUBMIT.

You're now ready to download the Testspace client to start pushing data

Install the Testspace Client


As a prerequisite to pushing test content the Testspace client console utility is required to be installed on your host computer. Refer to the client installation instructions for Windows, Linux, and Mac computers.

Verify installation:

$ testspace --version


YOUR.. is based on your setup! Nothing will work if the configuration is not correct.

You will need to provide your access token for credentials to push data to your Projects and Spaces. The token is obtained from your user settings described HERE. To simplify the command line for interactive use, set the default URL using the Testspace Clients' config command.

testspace config url

Push Some Data

After downloading and configuring the Testspace client as described above, there are a number of data files in the Getting Started repository on our Testspace Samples GitHub Organization that can be pushed from the console.

To get the example files:

The example test content files:

  • results[n].xml - two test result files in JUnit XML format.
  • analysis.xml - static analysis output.
  • coverage.xml - code coverage analysis output.

Push the files

Again the YOUR-space-name is based on your setup!

  testspace analysis.xml [tests]results*.xml coverage.xml "YOUR-space-name" 

Once pushed successfully, from the Project's Spaces tab, select the new Space which will take you to the Schema tab where you can review the results hierarchy and the data that was pushed. Select the Metrics tab to review the newly created charts for test suites, test cases, and code coverage.

For more information on How to Push Data - organize results, create folders, use incremental uploads, include git source code changes, and other push options.

What's Next?

For more details refer to our product blog at

Page Tools