So far, we have
- manually invoked a GitHub workflow to publish pre-canned results
- implemented and executed new test specs from scratch
- used branching when developing new test specs
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 by first creating a Testspace Project board.
To create a GitHub Project Board for Testspace, use the following steps.
- In your
testspace.getting-startedrepo, from the
New projectand use
Testspacefor 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:
Issues that are pushed during a Test Session are automatically added to the board in the "To do" column.
Let's on purpose fail some test cases, demonstrating how issues are auto-generated and managed using Testspace.
Create a new test session by clicking on the
New Test Sessionbutton and select only
In the active session, click on
Hello Manualand set the first case
Test Case Oneto 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. For
Blockedstatus options, by default, an issue will be generated. The
Do not reportoption can be used to override this default behavior.
titleis auto filled using a combo of the Status, Suite, and Case Name, this is editable though.
Test Case Twocase to Passed and complete the test Session.
On completion of the session an issue associated with the Failed test case will be automatically generated in GitHub and added to the
View the issue in the
To docolumn of the
An existing issue can also be appended to during subsequent executions of the test case that is referencing it.
- Create a new Test Session selecting
- Run the
- Set the test case status to Failed
- Add a textual description -
The test is still failing
- Complete the Session
The Github Issue will be updated with the new comment information.
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.
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 issueto GitHub
- New test session information can be
appendedto an existing issue
- A Project Board is used for managing the status of issues
- Boards are also used for Cycle management and Exploratory Testing observations (coming soon)