Test Interface

The test structure is auto generated based on some UI configuration. It provides functions to read & write parameters and to interact with external tools.

Test Entry Point

The tests are written in python. The following is an example of a generated test based on the configuration of one input parameter and one output parameter:

class contact(contact_BC):

    '''
    for debug purposes, a logger is available to log infomration and porpagate them to the UI.
    logging can be used as described below:
    self.log_info(<message>)
    self.log_debug(<message>)
    self.log_warning(<message>)
    self.log_error(<message>)
    self.log_measure(<message>)

    <do_not_touch>
    


    Input Parameter | Shmoo | Min | Default | Max | Unit | fmt
    ----------------+-------+-----+---------+-----+------+----
    ip.Temperature  |  Yes  | -40 |   25    | 170 | °C   | .0f

    Parameter         | MPR | LSL | (LTL) |  Nom  | (UTL) | USL  | Unit | fmt
    ------------------+-----+-----+-------+-------+-------+------+------+----
    op.new_parameter1 | No  |  -∞ |  (-∞) | 0.000 | (+∞)  | +∞   | ˽    | .3f
    </do_not_touch>

    '''

    def do(self):
        """Default implementation for test."""
        self.op.new_parameter1.default()

The do function is the main spot where test code should be located which will be automatically executed by the test program.

note: do should not be renamed oder removed as the test program will try to call this function on each associated test instance.

The test contains also some comments with some information of available parameter and some hints how to use the logger.

The following sections will cover all other interfaces that are provided by a test.

Input Parameter

The current parameter value by the test program could be extracted as follow:

temperature_value = self.ip.Temperature()

The temperature_value variable contains the value of the temperature set by the corresponding test program.

note: input parameters are read only parameters that shall not be overwritten in code.

Output Parameter

Output parameter on the other hand are more likely to change.

self.new_parameter1.default()
self.new_parameter1.write(1.0)
output_param_value = self.new_parameter1.get_measurement()

To operate on output parameter there are several public methods, i.e. default, write and get_measurement. As seen above, the function ‘default’ will assign a default value to the output parameter.

note: the value assigned with the default function will always be in the defined range and will always pass the test.

The write function assigns the output parameter a value, i.e. a test result. The value could be a measurement performed by a digital multimeter or from an other computation.

The get_measurement function gets the value assigned to the output parameter.

note: in case the mpr flag is set, the write function could be called multiple times and the value will be appended to a list. Calling the get_measurement function shall return a list of all written values.

note: output parameters must be assigned with a value before the test execution ends, otherwise an exception will be raised.

Context

The context is part of the test and could be used as follow.

self.context.<...>

The Context is a special object which provides the test access to all required tools. Tools are configured in the hardwaresetup section such as e.g tester, instrument and actuator.

The context could be seen as a container that manages all the tools and provides the test with the available interfaces to interact with it’s environment

Tester

The tester is a plugin instance which shall be used to operate on the real tester hardware and execute such operations like setting relays, reading channels, etc…

self.context.tester.<function>

The tester interface is not part of this document and shall be provided by the tester hardware developers.

proposal to simplify accessing the tester
self.tester.<function>
not implemented yet

note: the tester is a plugin and shall be installed separately.

Instrument & Actuator

Using instruments or actuator defined in the hardwaresetup section shall be done via the context.

self.context.<any-defined-instrument-or-actuator-name>.<function>

Some Remarks

Writing tests in an IDE such as Spyder IDE will simplify using the tools (e.g. tester, instruments, etc.) as it provides the user auto-completion support to easily explore the provided interfaces.