Tests CSV Overview
The Tests CSV file defines automated validation and simulation steps used during system verification. Each test describes which elements are injected or monitored, expected results, and how to compare outcomes. This is unrelated to DBSimGenerator, which is an offline ICD/code generator - the injection and result checks run directly in the CoreEngine runtime loop, which is why these tests are high-performance and accurate.
See How to Build an APIC System for Software Engineers for where unit tests (per model) and ATP tests (whole system) fit into the overall system-engineering workflow.
CSV Format
Test Name,Element,Injection Raw,Injection Eng,Result,Compare Operator,Timeout
Test1,LRU_FC.Control.State,,4,,
,LRU_FC.Control.Control,,,5,<=
Test2 in range,LRU_FC.Control.State,,2,,
,LRU_FC.Control.Control,,,2:8,,Column Description
| Column | Description | Example |
|---|---|---|
| Test Name | Test identifier. The same name in consecutive rows means a multi-step test. | Test1 |
| Element | Data path (LRU.Block.Element) referencing an ICD element. | LRU_FC.Control.State |
| Injection Raw | Optional raw data value (before scaling). | 0x04 |
| Injection Eng | Optional engineering-unit value to inject. | 4 |
| Result | Expected result value or range (e.g. 2:8). |
5 |
| Compare Operator | Comparison type between expected and actual results. | ==, <=, > |
| Timeout | Maximum wait time (ms) before declaring failure. Empty = wait forever. | 1000 |
Remarks
- Each test may span multiple lines; leave Test Name empty to continue the previous test.
- Compare Operators:
==,<,>,<=,>=,!= - Timeout: value in milliseconds; empty means wait indefinitely.
- Supported by Core-Engine App for automatic injection and monitoring.