In the previous section, we manually invoked a GitHub workflow to run fake test automation.
Now the tutorial will demonstrate executing a
Spec, using Testspace's manual runner. The example uses the Github repo you created based on the Setup section of the tutorial.
Let's execute a single
spec (aka test spec).
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.
Double click on
Next click on the
create a new session link:
Each spec is executed as an individual unit. In this example, we only have one spec -
Hello Manual, but there is no limit to the number of specs that can be included in a Test Session.
Now click on
For this example:
- Select the START button to begin execution
Passedfor the status of
Test Case One
Passedfor the status of
Test Case Two
- Add optional comments or images
- When done select the STOP button
Close the spec dialog.
Testspace provides multiple ways to view a spec's status.
Overall listing on the Manual tab reflects the latest status of all of the
test specs that have been executed.
Current tab represents the most recent published
Results for all tests, which can included published results.
And specifically the
Hello Manual spec that was executed.
The following file content is used, in this basic example, for running a manual test. Note that the
hello spec is an oversimplified example used for demonstration purposes only.
root └─ specs └─ 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 is located at
specs/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 specs is
- Refer here for changing the default location for test specs.
This section covered the running of a
- Specs are executed as individual units
- The status of specs are maintained within the Manual tab
- The status of specs, along with published automated results, are maintained within the Results tab