Skip to main content

Issues

So far, we have

  • manually invoked a GitHub workflow to publish pre-canned results
  • implemented and executed new test specs from scratch

This section of the tutorial walks through managing issues in the context of Testspace. Testspace integrates with GitHub Boards and GitHub Issues to leverage "already existing" and "widely adopted" functionality.

Let's start first by creating a Testspace Project board.

Setup Board#

To create a GitHub Project Board for Testspace, use the following steps.

  • In your testspace.getting-started repo, from the Projects tab click New project and use Testspace for Project Board Name
  • From the project template choose one of the three supported templates:
    • Basic kanban
    • Automated kanban (Recommended)
    • Automated kanban with reviews

Once the board is created go ahead and delete the 3 auto-generated notes - Welcome to GitHub Projects, Cards, and Automation.

Your board should look like the following:

Testspace Board

Push Issue#

Issues that are pushed during the running of a spec are automatically added to the board in the "To do" column. Let's now, on purpose, fail a test case, demonstrating how issues are auto-generated and managed using Testspace.

Click on Hello Manual and set the first case Test Case One to Failed. Notice the automatic settings for the ISSUES row. Feel free to add some textual description concerning the failed test case, such as This is a fake test failure.


Test Case Failed


- For `Failed` and `Blocked` status options, by default, an issue will be generated. - The `Do not report` option can be used to override the default behavior. - The issue `title` is auto-filled using a combo of the Status, Spec and Case Names.

The Failed test case will be automatically generated in GitHub and added to the Testspace board.

Issue Generated

You can also track the issue in the To do column of the Testspace board. Issue Added to Board

Append Issue#

An existing issue can also be appended to during subsequent executions of the test case that is referencing it.

  • Run the Hello Manual spec
  • Set the test case status to Failed
  • Add a textual description - The test is still failing

The Github Issue will be updated with the new comment information.

Issue Appended

Close Issue#

When an Issue is closed via GitHub the status is automatically reflected in Testspace. It is also moved to the Done column on the Testspace GitHub project board.

Recap#

Testspace supports issue management, which is essential when communicating with the development team. The following built-in functionality has been covered in this section:

  • When a test case fails the default setting is to Push new issue to GitHub
  • New test case execution information can be appended to an existing issue
  • A Project Board is used for managing the status of issues