PaceWords Reference

PaceWord guide lines

  • Use clear and descriptive test case names, e.g. Open Help Page

  • Use [Documentation] to explain the purpose of the test case

  • Make test case as readable as possible

  • Leave empty line after 10 lines, use Log to describe next section

  • Use [Tags] for running selected test case groups, e.g. ok or not ok when designing new test cases

  • Appstate must be the first step in a test case; navigation to pre-condition

  • Do not use Sleep keyword

  • Try to avoid extended use of project specific keywords, no more than 100 keywords total per project

  • Use teardowns to close the test session properly

AppState

First keyword of every test case is AppState. It is the pre-condition of a test case and a navigation system across different states in the system under test. It speeds-up test execution time significantly providing simple and efficient way to manage hundreds or even thousands of independent test cases.

Adding back to the AppState step at the end of a test case will speed up test execution, particularly when using computer vision based test automation.

PaceWords explained

Pace writing style

Contrary to good programming guides, test automation code should not use many functions (keywords). In programming, functions provide readability – and good function names show the intent of a programmer. In test automation, program is used several different ways, many incorrect, and this would result lot of keywords that are used once. When number of unique keywords is over 100, test automators cannot remember them all and test automation development slows down.

Common PaceWords

ClickElement Click element specified by xpath.

ClickText

Click text on web page.

DropDown

Select a drop down item.

HoverText

Move mouse on top of a text.

TypeText

Type given text to a text field.

VerifyElement

Verify element on the page and it is visible.

VerifyText

Verify page contains given text.

VerifyValue

Verify value in a given element.

Pace writing style emphasises using few steps. 80% of the steps should be using these:

  • ClickText

  • TypeText

  • VerifyText

PaceWords and parameters

PaceWords aim to describe a single user action. Their parameters are typically in this order:

  • PaceWord

  • Locator

  • Text to type

  • Anchor

Finding elements

Pace test automation system finds elements based on their closest texts. For example:

TypeText    Asiakasnumero    0123456789-A

Searches for input element which is close to text Asiakasnumero and then writes the text 0123456789-A to that input element.

Using anchors

Often page contains duplicate texts and you need to differentiate between the two. In these cases you need to specify an anchor, which is an unique test close to the correct one.

Handling windows

Sometimes application opens a new window when testing. For example QWeb doesn’t automatically set this window to be active so you need to do it yourself in the test with these PaceWords:

  • OpenWindow – Opens a new empty window and sets it active

  • SwitchWindow – Sets window active

  • CloseWindow – Closes current active window