Test Setup File
Description
Section titled “Description”A test setup is a XML file which contains the instruction set of the various test cases. The contents test setup file can be divided as follows:
Test setup :=
- Test Setup: Test setup file contains two sections Header and Test Case List
- Header: Header contains the basic information regarding to the test setup file, like versions, report file path, database file path, ECU name, tester information etc. User has to provide the information. Some values are optional and some are compulsory. Database path is a compulsory value. Check the table below for the required and optional fields.
- Test Case List: Test Case List contains a collection of test cases. User has to create the test cases.
- Test case: A test case is the collection of test steps such as send, wait, replay, verify.
- Send: This is a collection of send_messages. This test step instructs to send the specified messages.
- Send Message: This provides the details of message to be send. User has to initialize the messages and its signals. The default value assumed to the signals is 0. The message value my be given in engineering value mode or in raw value mode.
- Wait: Wait node instruct to wait certain period of time, expressed in terms of milliseconds.
- Replay: Replay node instructs to replay BUSMASTER log file.
- Verify: This is a collection of verify_messages. This test step instructs to verify the specified messages (both Rx and Tx).
- Verify Response: This test step verifies the specified message responses (Rx Messages) with in specified time. So this step requires a time interval.
- Verify Message: This provides the details of message to be verify. The user needs to formulate the validation condition. In the formula current signal value shall be denoted by ‘x’ following the algebraic notation. The presently supported logical operators are the eight: ==, >, <, >=, <=,!= , ||, and &&. By combining them suitably the following validation operations may be carried out: Range of values; e.g., (x <= 10) && (x >= 50) Set of discrete values; e.g., (x == 10) || (x == 20) || (x == 50) Formulation of any other validation procedure.Here is a sample test file: SampleTestSetupFile.xml.
The table below contains a concise description of each of the section details and error handling procedure in case of absence of any information.
| Section (tag) | Description | Assumed value if absent | Error condition if absent |
|---|---|---|---|
| Section (tag) | Description | Assumed value if absent | Error condition if absent |
Test setup (testsetup) |
The root node. Accompanied by its title (title) and version information (version) | - | Fatal |
Database file (database) |
Database file | Fatal | |
Version (version) |
Version information of the test setup | 1.0 | No error |
Module Name (module name) |
Module focused on for the testing | - | No error |
| Engineer’s name | Test engineer’s name | - | No error |
| Engineer’s role | And role / designation | - | No error |
Report file path (path) |
Particular of the report file to be generated. | Current working directory with the name same as the test setup. | Error |
Report file format (format) |
Format of the report file. Can be one of TXT and HTM | TXT | Warning |
Report file time mode (timemode) |
Time mode. Can be one of SYS (system), REL (relative) and ABS (absolute) | SYS | Warning |
Bus type (bustype) |
Bus type. At present can be only CAN | CAN | Fatal |
Test case list (list_of_test_cases) |
Collection of test cases. | Nil | Error. There must be at least one entry. |
Test case (testcase) |
Collection of test steps. A test case contains identifier, title and exception handler. The last one instructs if in case of failure to continue or exit. | Nil | Error. There must be at least an entry. |
Test case title (title) |
Test case title | - | No error |
Test case exception handler (exp_handler) |
Instructs if in case of failure the testing process exists or continues. Can be one of continue or exit | continue | Warning |
Transmission (send) |
Collection of the messages to be transmitted. | - | No error |
Transmittion message details (send_message) |
Details of the message list to be transmitted. | Nil | Warning |
Send message id (identifier) |
Identifier of the message. | - | Error. The test case shall be dropped. |
Send message unit (unit) |
Unit type of the signals. Can be either raw (raw) or engineering (eng) | Engineering value | Warning |
Signal (signal) |
Details the signal with its name (name) and value. | - | Error. The test case shall be dropped. |
Verification (verify) |
Verification instruction set. Contains a collection of verification messages. | Nil | Error. A test case must have a validation routine. Test case shall be dropped. |
Failure classification (failure) |
For a verification procedure – how to classify validation failure. Can be one of warning, error, fatal | Error | Warning. |
Verify message details (verify_message) |
Details of the message list to be verified / validated. | Nil | Error. The test case shall be dropped. |
Verify message signal detail (signal) |
Details of a signal under a verify message node. The attribute required is the signal’s name (name). The node value shall be a string with formulation of the condition. This shall follow the syntax mentioned in the table below. | Nil | Error. The test case shall be dropped. |
So, As explained above the test setup file has to write in XML format. So user has to know the syntax of XML and the test set up file. But To simplify this process BUSMASTER provides an editor called Test Setup Editor.
Authoritative source: BUSMASTER DITA help source test_setup_file.dita, compiled into BUSMASTER.CHM with the application.