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.
New Test Session dialog:
- Add a name for the session - e.g.
First test session
- Add an optional description (e.g.
- Select the
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.
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
- If you are not the test assignee, defaults to unassigned, a notice will appear asking you to self-assign. Please do that now.
Passedfor the status of
Test Case One
Passedfor the status of
Test Case Two
- Add optional comments or images
- Close the dialog box
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
- Updates the
Overallstatus for all the suites
- Publishes the
Once a session has been completed no additional updates can be made.
Testspace provides multiple ways to view a test spec's status.
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.
Current tab represents the most recent published
Results for all tests.
And specifically the
Hello Manual test spec that was executed.
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 ...
The Testspace configuration file
.testspace.yml is required at the root with the following minimun content:
.testspace.ymlfile, specs will not be visible in Testspace
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
- Manual tests are maintained in the code section of a
repousing folders and markdown files. The default folder location for test specification files is
- Refer here for changing the default location for test specs.
- In this example, the sub-folder
manualis used for storing the results in a separate folder, where the
automatedresults use a similar sub-folder.
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 Testslisting and
Publishes the Results