Manual test syntax

Use markdown to add steps and to format text.

Test syntax

When working in text view, use the following syntax to add steps:

Item Details
Setup or regular steps

Each step starts with a hyphen and a space.

Example: - Navigate to the Web site.

Validation steps

Each step begins with a hyphen, space, and question mark:

Example: - ? Validate that the page loaded correctly.

Call to step

Each step begins with a hyphen, space, and the @ character with the ID number of the test to call:

Example: - @1102 Search by user

Parameter

Syntax: <parameter name>

Example: Use port number <port>

For details, see Using parameters in tests.

A step can span more than one line. You do not need to put a hyphen and space on other lines if a step continues.

Tip: When working in text view, a red X displays next to any lines with syntax or logic errors. For example, a call step cannot call its own test.

Back to top

Format text in the test script

Use markdown in your test script to emphasize text and display it in bold, italics, underline, or colors (red, green, blue).

Aside from the text view of the steps, all other displays of the test script will include the formatted text (for example, list view and grid view of the steps, Manual Runner, and Run report).

To format text:

Use the following syntax to format your test script:

Bold **text**
Italics *text*
Underline __text__
Red {text}red
Green {text}green
Blue {text}blue

For example:

- Display the following in bold: **bold**
- Display the following in italics: *italics*
- Display the following underlined: __underline__
- Display the following in red: {red}red
- Display the following in green: {green}green
- Display the following in blue: {blue}blue

The list view displays the formatted test script:

Note:  

  • HTML tags are not supported in scripts. Using HTML tags as part of the script can lead to unexpected behavior.
  • You can combine formatting.

    Example: *You can **combine** formatting* will display as You can combine formatting.

  • If the test script includes an asterisk or double-underscore in the middle of a word or followed by a space, the character will display as-is in the script.

  • To force an asterisk or double-underscore at the beginning or end of a word to display literally in the test script, and not behave as a special character, add a backslash before the character. Example: \*word\* will display as *word*.
  • Another way to disable formatting, and force special characters to display literally, is by surrounding the text with backticks. Example: `__underline__` will display as __underline__

Back to top

See also: