Visible to Intel only — GUID: GUID-3958DCB2-9DA3-4FAB-8B0D-EB73A3961F44
Visible to Intel only — GUID: GUID-3958DCB2-9DA3-4FAB-8B0D-EB73A3961F44
End-to-End and Setup Validation Guidelines
All of the functional and end-to-end validation must be covered by the validation team which is assigned for validating the application. This section defines the validation scope with special emphasis on setup coverage, which is usually project-specific.
E2E Validation
After covering both the trusted application and host-side application validation, it is time to move to full system testing. The idea here is to cover real functional use cases which involve all of the different components. This includes our components and the different parts which are defined by the chosen setup (see below).
Back-end Support and Timing
Some of the APIs require back-end support (e.g. Sigma and Capability Licensing Service). Validating those is significantly different when using pre-production setup in opposition to production setups.
For pre-production, simple local solutions might be used, but eventually the full end-to-end setup with the real production servers must be used and covered in production setup.
Setup Coverage
Validating the application in various setups is critical for ensuring functionality in all planned production setups.
In your setups, the following should be covered:
- Hardware - Platform type and generation, CPU, PCH, etc.
- Firmware - firmware kit: version, 1.5M/5M, firmware settings - e.g., SKU settings via FITC, BIOS, pre-production/production, different certificates, etc
- Software - operating systems (flavors, x32/x64), user permissions, platform drivers, Intel® Management Engine Interface (Intel® MEI) installer, etc.
- General SKU Matrix validation (with fused production parts)