In Qentinel Pace, test cases are written using PaceWords. PaceWords are keywords which are developed and maintained by Qentinel. They enable you to write test cases with high readability, usability and robustness. PaceWords are platform agnostic keywords, which mean you can pretty much use the same PaceWords to write test cases testing mobiles, browsers or native operating system applications. The easiest way to get familiar with writing tests using PaceWords is to examine the starter's template.

  1. Create a project

  2. Create a robot

  3. Create a suite

  4. Click on starter suite


A starter suite is created. Click on the editor icon </> to view the tests.


The recommended repository structure is shown here. Typically, you will need resources folder and test folder. File containing your keywords and locators reside under resources, whereas the actual test cases reside under tests as .robot files. Click on the tests folder and starter.robot file. You will see the test cases in editor. This are template test cases following the best practices of creating tests. Feel free to execute them.

An example test case

Test the global home page
[Documentation]     Accepts the cookie policy, changes the
...        location to 'Global' and verifies home page text.
    [Tags]              Home
    Appstate            home
    ClickText           Accept
    ClickText           Change location
    ClickText           Global
    VerifyText          Robotic software testing. Qentinel Pace


AppState is a pre-condition of a test case. It sets Application(s) under test to correct, known state. First keyword of every test case is Appstate. It is a navigation system across different states in system under test, or between separate applications. They are typically set under resources folder, keywords.robot file.

Please note that PaceWords are continuously developed and maintained and hence refer to the latest version of PaceWord documentation.