Skip to content

3. Standards: Levels of Test for Vendor Layer

Jump to bottom
Ulrond edited this page Jul 11, 2024 · 8 revisions

Level of test for the Vendor Layer

Once the documentation is approved testing requirements can be defined based on levels of test, these must allow for phased delivery, and be capable of being run by the vendors. These levels of test are grouped together and called the VTS ( Vendor Testing Suite ).

Level 1: Component Function Testing (Isolated Component Environment, Pre-Commit) – Vendor Testing

  • Purpose: API Function testing of individual components + requirements documentation
  • Scope: Thorough testing if each function and parameters
  • Execution: Perform by component engineers during initial pre-commit interface development or when modifying existing components, before commit.

Level 2: Component Unit Testing (No upper stack layers, Pre-Commit) - Vendor Test

  • Purpose: Focused testing of individual modules in a component, aligned with requirements documentation. Scope: Independent component testing
  • Scope: Verifies the independent functionality of each module within a component.
  • Execution: Performed by component engineers pre-commit during initial development or when implementing changes.

Level 3: – Component External Stimulus Testing (No upper stack layers, Pre-Commit) - Vendor Test

  • Purpose: Pre-commit testing using external stimuli to validate component responses and adherence to requirements.
  • Scope:
    • May trigger both Level 1 (Component Function) and Level 2 (Component Unit) tests for deeper verification.
    • Includes specific tests designed to interact with external devices and evaluate component behavior.
    • Infrastructure: Requires specialized setup, either on engineers' desks or in dedicated racks, and runs on vendor-provided equipment.

Level 4: Layer Integration Specific In-Depth Testing( Isolated Layer, Pre-Automation) – OEM Level Test

  • Purpose: Comprehensive testing of a specific layer, focusing on performance, stress tolerance, and other in-depth requirements.
  • Scope:
    • Isolates the layer for analysis, excluding upper stack layers.
    • Performed on an as-needed basis, not as part of a regular automated test suite.
    • Execution: Conducted by OEM, integration of multiple vendors.

Level 4: Layer Integration Tests (Upper Stack Layers Required) – OEM Test

  • Purpose: Verifies the functionality of a layer when integrated with upper stack layers. Testing may trigger integration tests of dependent layers for comprehensive validation.
    • Infrastructure: Requires access to internal infrastructure for a realistic testing environment.
    • Milestone: This level of testing may serve as a release point for stack layers.
Clone this wiki locally