Russian version | All documentation
Use the tables below to choose a verification procedure. Each procedure describes preparation, actions, and expected results. A successful build, a unit-test result, a server operation, and a visual observation provide separate evidence.
| Document | Purpose |
|---|---|
| Developer tools panel | Run preparation and comparison tools through explicit forms. |
| Test server reference | Prepare all test plugins, configure the server, and collect reports. |
| Server compatibility | Check supported components and platform requirements. |
| Manual testing procedure | Connect the client, run scenario steps, and record results. |
| Materials test plugin | Use the material-effect test scenes and in-game menu. |
| Studio content preparation | Generate models, materials, labels, and maps for rendering checks. |
| Area | Procedure or cases |
|---|---|
| Radar scenarios | Manual test cases and role/outcome matrix |
| Radar layers | Verification procedure and acceptance cases |
| Studio rendering | Rendering verification and rigid instancing |
| Material editor | Scene verification |
| Performance monitor | Runtime checks |
| Document | Purpose |
|---|---|
| Renderer diagnostics | Capture renderer state and inspect the resulting files. |
| Image comparison | Compare prepared captures and set difference thresholds. |
| Matgen regression checks | Verify material validation, UV output, and edge-wear baking. |
| Developer tools verification | Check command construction, translation, launch scripts, and files produced by generators in the test cases. |
| Native module installation and NitroApi checks | Verify the CMake installation recipe in temporary destinations and check the built NitroApi library's public interface. |
| Windows installer checks | Verify new installation, ZIP updates, cancellation, recovery, and removal on synthetic files. |
| Repository test targets | Select CMake test targets and the required configuration. |
Record the relevant source revision, build configuration, installed artifacts, selected scenario, and result. Reuse passing evidence for an unchanged source and configuration snapshot; repeat checks when the affected behavior changes or a concrete concern requires it.