Documentation Acceptance Test

This is the release gate for the manual itself. A production manual is not accepted because it is detailed; it is accepted when an engineer can follow it against the shipping customer package without repository knowledge or undocumented developer steps.

Required test environment

Use a clean or reset Windows workstation representative of a customer machine. The tester should receive only:

• the customer installation package;
• the customer license/activation material;
• this documentation bundle;
• the supported external hardware required for the selected acceptance lanes.

The tester should not use the development repository, internal patch notes, source code, developer scripts, or unpublished tribal knowledge.

Gate A — install and activate

Execute the Installation chapter verbatim.

Pass criteria:

• all paths named in the manual exist or the documentation clearly explains a packaging variant;
• installation does not require a source checkout;
• version, license verify/status and doctor work exactly as written;
• required data roots can be created with the documented permissions.

Gate B — first 60 minutes

Execute First 60 Minutes from a new terminal.

Pass criteria:

• every command parses in the shipping CLI;
• expected results are understandable to a new user;
• no command depends on a repository-relative file;
• a support bundle can be produced without developer tools.

Gate C — protocol golden runs

Run all protocols included in the release/edition:

Any lane not executed must be marked not accepted for publication as an unconditional claim.

Gate D — gRPC and automation

Pass criteria:

• integration serve starts from the installed path;
• health and capabilities succeed;
• session lifecycle smoke succeeds;
• canonical signal list/read/write/smoke examples use the exact shipping syntax;
• remote security configuration is documented if remote access is part of the edition.

Gate E — NI VeriStand Native Gateway

Use the release-note supported NI version.

Pass criteria:

1. VeriStand project deploys independently.
2. gRPC health passes independently.
3. NativeClientBroker and OperatorLauncher files are present in the installed package.
4. Gateway configuration uses only documented customer-editable fields.
5. Signal mapping works in both required directions.
6. Heartbeat/watchdog behavior is visible.
7. Emergency-stop/isolation/watchdog tests fail safe on the approved bench.
8. Guarded shutdown exits the workflow cleanly.
9. No ASAM XIL dependency is needed for the current gateway.

Gate F — test packages and reporting

Pass criteria:

• package catalogue matches the installed/licensed product;
• PICS/PIXIT generation/selection works as documented;
• a small campaign can be planned and run;
• PASS/FAIL/BLOCKED/SKIPPED/ERROR meanings match product output;
• report and evidence paths are correct;
• redaction/support-bundle procedure works on produced artifacts.

Gate G — responsive documentation

Test the generated site at minimum on:

• desktop width around 1440 px;
• tablet portrait and landscape;
• phone width around 320-430 px.

Pass criteria:

• no primary content is clipped horizontally;
• code blocks/tables remain usable;
• hamburger menu opens/closes and keyboard Escape works;
• active navigation item is visible;
• sticky mobile footer does not cover content;
• logos remain legible without dominating the header.

Command audit

For each copy/paste block:

1. run the command against the shipping binary;
2. verify every option with <command> --help;
3. remove developer-only flags, patch identifiers and repository paths;
4. replace hard-coded lab NIC/certificate/channel values with clearly marked customer placeholders;
5. record the tested product version.

Acceptance record

The documentation is ready for customer publication only when failed gates are corrected or explicitly scoped out in the release notes and capability matrix.