Write & Run a Spec
This step writes a Manual test spec and runs it, all in Testspace, in the main Space. No repository or local files are needed.
Write a Spec
- Click the
mainSpace and select its Manual tab. - Click New Spec.
- Enter the following under Spec Content (Markdown):
# 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
A spec has a name (the # heading, an <H1>) and one or more test cases (each ## heading, an <H2>). Testspace adds the spec's front matter for you, so don't type it here.
- Click the Preview tab to see the spec as a tester will, then click SUBMIT.
Run It
- On the Manual tab, click Hello Manual to open it.
- Click START. Testspace asks what context to run in, with Ad hoc, outside any formal test session selected: click OK. (Sessions come later in the tutorial.)
- Select Passed for
Test Case One, and again forTest Case Two. - Add comments or images if you like. Below the cases, Observations is for notes about the spec as a whole, such as findings from exploratory testing (Exploratory).
- Click STOP, then close the dialog.
Running a single spec like this, outside a Test Session, is an ad hoc run.
Status
The run's status shows in two places.
Manual Tab
The spec's row on the Manual tab shows its last run:
- Status: 2 passed
- Tested: when it ran, then Ad hoc, how long the run took and who ran it
The ·Overall· panel beside the list sums up every spec: here 100% coverage (2 tested), 100% passing (2 passed) and 2 test cases in 1 spec.

Current and Results Tabs
Each run is saved as a Result, named after the spec: Run 'Hello Manual' spec. It becomes the Space's active Result, shown on the Current tab, and is listed on the Results tab next to the Result you published. The Hello Manual spec appears in it as a Suite with a flask icon.
Review Results looks at both Results.
Read More
Specs can do much more than this one; see Writing a Spec for the full syntax:
- Markdown: lists, tables, images and links in any step
- Variables, includes and conditions, with Liquid
- To-Do checklists a tester ticks off step by step
- Notes, warnings, tabs and collapsible sections
- Includes: steps written once and shared by many specs
- The editor's toolbar, which inserts all of these for you
Recap
This section covered:
- Writing a spec in Testspace's editor, and checking it with Preview
- Running the spec ad hoc, with START and STOP
- Where its status shows: the spec's row and ·Overall· on the Manual tab, and a Result on the Current and Results tabs