Historically, Test Management tools have focused on manual execution and the management of test team activities. But with the evolution of Continuous Integration, Continuous Testing, and DevOps much of a software project’s quality assessment is now driven by automation.

Automated testing can leverage the GitHub platform and Continuous Integration tools using machines to execute tests daily or with every software change committed resulting in a continuous stream of test results.

In contrast, dedicated QA staff activities are typically managed as a separate team using its own processes and toolset. Specific builds are targeted for testing, producing a lower volume of test results due to the constraints of time and test resources.

Having disconnected teams, workflows, and toolsets creates challenges and barriers to obtaining a holistic view of the health of a project.

Connecting the Workflows

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

  • Test instructions, captured using plain text and markdown, are managed in repositories following the same process as development (version control, code reviews, etc.).
  • GitHub Project Boards are used to schedule and manage testing activities and resources.
  • The Status of the software, regardless of the testing method, is seamlessly aggregated in Testspace.

Testspace connects the workflows, toolsets, and test results of automated and manual testing




Specifying Manual Scripted Tests

We’ve standardized on the Gauge test format - a flexible, open source specification syntax from ThoughtWorks.

Test specifications are written in natural language (plain text) in a format that can be reused by automation. A simple example with two specific test cases follows.

Test Specifications in Repo

For details on the test format refer here.

Creating Test Plans

GitHub Project Boards are used to create and manage test plans. Testspace, on notification of project creation, populates the board with Cards for all tests specified in the repository.

Repo Projects for managing

Testers are automatically assigned to execute tests based on the Project Board. The Notes corresponding to the tests are automatically updated with status.

Testers can execute independent of GitHub, project stakeholders can manage and track independent of Testspace

Executing Manual Scripted Tests

Testspace is used to execute manaul tests with its built-in Runner.

Test runs




Aggregatting Results from Manual and Automated Tests

Although most Test Management applications provide a means (i.e. API) to include automated tests results, they’re ill-suited for handling the large volumne of results typically generated by automated CI systems. Testspace was specifically designed for high volume automation. It aggregates data from all your build and test systems and performs analysis on the content.

See our article on Testspace Integration with GitHub for CI testing

To upload content to the Testspace server only a single command is required:

testspace result*.xml coverage.xml log.txt .. 

For manual execution, all status, notes, and observations entered by the tester are collected by the built-in test runner.

The Status of the software, regardless of the testing method, is seamlessly aggregated. All the metrics; test results, code coverage, defects, requirements, etc., are collected and used together.

Aggregated reporting

See our article on Test Analytics and how it is applied to the data collected. And for more advanced metric collection see our article on creating custom graphs.




Get setup in minutes!

Try Testspace risk free. No credit card required.

Have questions? Contact us.

Testspace works seamlessly with the vast majoritiy of CI systems and online services, including

Travis CI Circle CI Jenkins Appveyor Shippable GitLab CI Bitbucket Pipelines