Skip to main content

Publish Overview

Testspace supports publishing large volumes of automated test results with a single command, including code coverage, static analysis, and other important metrics.

Because of its built-in CI integrations with GitHub, GitLab, and other systems, branching, forks, and pull requests work seamlessly with the developer workflow. Testspace will also automatically aggregate test results from parallel jobs.


GitHub Actions - Testspace aggregates results for jobs, matrix, and even multiple workflows

Testspace also includes support for in-house proprietary automation systems.

The following content is a partial .github/workflows/ci.yml file for example purposes:

name: CI
runs-on: ubuntu-latest
- uses: actions/checkout@v3
- uses: testspace-com/setup-testspace@v1
domain: ${{ github.repository_owner }}
- name: Do testing stuff
run: your-test-framework --tests
- name: Push result to Testspace server
run: |
testspace ./results/*.xml coverage.xml
if: always()

The following is an overview of the functionality provided by Testspace:

To publish content to the Testspace server simply "push" file(s) with the Testspace client.

testspace path/to/**/results*.xml coverage.xml ..

Once test results have been published, the status of the software, regardless of the testing method, build system, etc., can be monitored by all team members. All the metrics - test results, code coverage, defects, etc., are collected and analyzed.

Test Results


The Testspace client was designed to support large volumes of content

Once test results have been published; the Testspace Dashboard provides:


Quality can be assessed not only using test results, but with other metrics like code coverage, and custom metrics (i.e. timing, error logs, etc.).