QUTest™ Script Reference

QUTest™ Fixture ReferenceQView™ Visualization & Monitoring

A QUTest test script contains a group of related tests (a test group). The basic job of these tests is to send commands to the test fixture running in the Target and to compare the QSPY textual output produced by the Target with the test expectations.

The QUTest test scripts are executed in the host by the QUTest script runner that communicates with the QSPY host application via the UDP interface. The QUTest script runner is itself implemented in a Python module qutest.py.

QUTest™ Testing DSL

The Python module qtools/qspy/py/qutest.py defines a small Domain Specific Language (DSL) for writing test scripts in Python. The structure of this DSL is very simple. Each test script consists of two sections:

Preamble

The "preamble" section of a test script file specifies include scripts and defines callback functions common to all tests in this file. It can contain the following functions:

• include()
• on_reset()
• on_setup()
• on_teardown()

The on_...() callback functions can call any of the test commands.

Tests

The "tests" section of a test script file contains the actual tests. Each test starts with the test() command and can contain any number of the test commands. The test continues until another test() command, or the skip() command.

• test()
• scenario()
• skip()

Commands

The commands that you can place in the tests (as well as inside the callback functions) are:

Simple Commands:

• glb_filter()
• loc_filter()
• ao_filter()
• current_obj()
• poke()
• fill()
• continue_test()

Complex Commands:

• command()
• query_curr()
• init()
• dispatch()
• post()
• publish()
• probe()
• tick()
• peek()

Commands that don't communicate with the Target:

• expect()
• expect_pause()
• test_file()
• test_dir()
• last_rec()
• pack()
• note()
• tag()

QUTest™ Fixture ReferenceQView™ Visualization & Monitoring