Share this page

# Manual test syntax

Use markdown for adding steps and for formatting text.

In this topic:

## Test syntax

When working in the Text Editor, use the following syntax to add steps:

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 Use parameters in tests.

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

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

Basic example

    - Enter user name.
    - Enter password.
    - Press <ENTER>.
    - ? Was login successful?

Example that calls another test

    - @1005 Call <Log into shopping cart>
    - Scroll up and down to review the cart.
    - Select the item(s) to delete from the cart.
    - Click <DELETE>.
    - Confirm the deletion.
    - ? Is the display of the cart empty?

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 editor, all other displays of the test script will include the formatted text (for example, the Visual Editor, Manual Runner, and Run report).

To format text:

In the Text Editor, 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 Visual Editor will display the formatted test script:

Note:

- 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:

- Create Gherkin tests
- Automated testing flow (pipelines)
- Create test suites
- Track and analyze product quality

https://admhelp.microfocus.com ALM Octane 8942
Tips to improve your search results... ValueEdge & ALM Octane Help Center ValueEdge ALM Octane Help 16.0.100-16.0.400 All View Local Help Center View Online Help Center back Go back in browser history forward Go forward in browser history Remove search highlights next topic Go to next topic previous topic Go to previous topic Print the current topic Version: