Run Manual

This tutorial demonstrates executing test specs using Testspace's manual runner. This example uses a Github repo you created based on the sample repo in the getting.started section of the tutorial.

Test Session

A Test Session is the vehicle used for running manual tests in Testspace. A session is defined as a collection of one or more individual test specs to be executed.

In Testspace, click on the main space of the project associated with your repo. Next, select the Manual tab to display a listing of all available specs.

Create your first test Session by clicking on the "New Test Session" button.

From the New Test Session dialog:

• Add a name for the session - e.g. First test session
• Add an optional description (e.g. Getting started)
• Select the Hello Manual spec
• Select SUBMIT

Upon creation of the new session, by default, the session is highlighted as active. Only the test specs selected for this "new" session are listed. In this example only the Hello Manual test spec has been selected.

Note: A good process practice is to create a new session for each build tested.

Run

Each test spec is executed as an individual Suite. In this example, we only have one Suite - Hello Manual, but there is no limit to the number of Suites that can be contained in a session.

For this example:

• Using an active session, click on the Hello Manual suite
• If you are not the test assignee, defaults to unassigned, a notice will appear asking you to self-assign. Please do that now.
• Select Passed for the status of Test Case One
• Select Passed for the status of Test Case Two
• Add optional comments or images
• Close the dialog box

Complete

Once the selected Suite(s) have been executed, the session can be completed. This is done by clicking on the blue check icon in the test session box.

Completing a Test Session:

• Removes the active session from the Manual tab
• Updates the Overall status for all the suites
• Publishes the Results

Once a session has been completed no additional updates can be made.

Status

Testspace provides multiple ways to view a test spec's status.

Listing

The Overall listing on the Manual tab reflects the latest status of all of the test specs that have been executed and completed within Test Sessions.

Results

The Current tab represents the most recent published Results for all tests.

And specifically the Hello Manual test spec that was executed.

Files Used

The following file content is used in this basic example of running a manual test. Note that the hello test spec is an oversimplified example used for demonstration purposes only.

root
  └─ specs
      └─ manual
           └─hello.md
  ├─ .testspace.yml
  └─ README.md
  ...

.testspace.yml

The Testspace configuration file .testspace.yml is required at the root with the following minimun content:

manual:

Without the .testspace.yml file, specs will not be visible in Testspace

hello.md

The hello spec file was located at specs/manual/hello.md using the following content:

---
testspace:
---

# Hello Manual
This is a manual test.

## Test Case One
Some description here.

* check this
* check that

## Test Case Two
Some description here.

* check this
* check that

Notes:

• Manual tests are maintained in the code section of a repo using folders and markdown files. The default folder location for test specification files is specs.
• Refer here for changing the default location for test specs.
• In this example, the sub-folder manual is used for storing the results in a separate folder, where the automated results use a similar sub-folder.

Recap

This section covered the following executing test specs:

• Create a Test Session containing one or more test specs
• Execute each test spec as an individual "runnable" Suite
• A Test Session is required to be Completed
• Completing a Test Session updates the All Tests listing and Publishes the Results