When reading the documentation on the pytest-f3ts plugin, we will be using the following terminology:

• Test Plan

  • A structured file or set of instructions that outlines a collection of test cases and/or test phases designed to be loaded and executed in a specific order. It serves as a roadmap for the testing process.

• Test Phase

  • A grouping of test cases within a Test Plan, executed sequentially. Test Phases are typically used to organize tests based on specific criteria, such as testing stages or hardware components.

• Test Case

  • A specific action, measurement, and assertion designed to test a given requirement. For example, a Test Case might involve applying a specific voltage to a PCBA component and measuring the output to ensure it meets design specifications.

• Test Configuration

  • The set values used to set test limits, ID and Error numbers, and other test plan-specific settings. These configurations can be established in a configuration file or through a graphical user interface.

• Test Interface

  • A pytest fixture that provides access to various hardware test equipment and instrumentation used by the test plan. The Test Interface may also include software tools or libraries that facilitate the testing process.

Acronyms

We use the following acronyms throughout our documentation:

• ADC: Analog-to-Digital Converter
• API: Application Programming Interface
• ATE: Automated Test Equipment
• CAN: Controller Area Network
• CI/CD: Continuous Integration/Continuous Deployment
• CLI: Command Line Interface
• DAC: Digital-to-Analog Converter
• DFT: Design for Testability
• DIO: Digital Input/Output
• DMM: Digital Multimeter
• DUT: Device Under Test
• DVT: Design Verification Testing
• GUI: Graphical User Interface
• I2C: Inter-Integrated Circuit
• IDE: Integrated Development Environment
• PCBA: Printed Circuit Board Assembly
• PVT: Production Verification Testing
• SPI: Serial Peripheral Interface
• UART: Universal Asynchronous Receiver-Transmitter
• USB: Universal Serial Bus