Skip to main content
Version: Next

PCR.AI Software Test Documentation (STD)

Version: 3.0.0 Date: January 2026 Status: Complete


1. Purpose

This Software Test Documentation (STD) set describes the test approach, test infrastructure, and test artifacts for PCR.AI v3. It follows IEEE Std 829-2008 (Standard for Software and System Test Documentation) with tailoring appropriate for a cloud-based SaaS application.

The STD provides complete test coverage for all requirements defined in the SRS, enabling:

  • Verification that implementation meets requirements
  • Traceability from requirements to test artifacts
  • Consistent test method selection across domains
  • Regulatory compliance evidence

2. Audience

ReaderUse Case
QA engineersTest execution, test case reference, automation implementation
DevelopersUnderstanding testability requirements, HTML attribute conventions
Technical leadsTest coverage review, release readiness assessment
Regulatory reviewersValidation evidence, test traceability to requirements

3. Coverage Summary

MetricValue
Total STD Documents99
Domain STDs29
Rule STDs61
Root Documents9
Requirements Covered405
Test Cases (Domains)459
Test Vectors (Rules)1,350
Total Test Artifacts1,809
Overall Coverage100%

4. Document Index

4.1 Root Documents

DocumentDescription
std-introduction.mdThis document - overview and index
std-test-plan.mdTest method selection policy and strategy
unified-traceability-matrix.mdRequirements to test case mapping
unified-coverage-report.mdCoverage metrics and gap analysis
std-ui-testability.mdHTML attribute naming conventions for automation

4.2 Domain STDs

Test specifications for functional domain requirements (29 documents in domains/):

DomainDocumentREQsTest Cases
Analyticsstd-analytics.md26
Analyzerstd-analyzer.md14
Audit Logstd-audit-log.md411
Client Configstd-client-config.md313
Commentsstd-comments.md1019
Config I/Ostd-configio.md1421
Error Codesstd-errorcodes.md1118
File Importstd-fileimport.md1323
Filtersstd-filters.md110
Global UIstd-globalui.md917
Helpstd-help.md515
Introduction (SRS)std-introduction-srs.md00
Keyboardstd-keyboard.md28
Kit Configstd-kitcfg.md2842
Known Issuesstd-known-issues.md00
NFRstd-nfr.md512
Notificationsstd-notif.md511
Printstd-print.md56
Progressstd-progress.md411
Reanalyzestd-reanalyze.md816
Reportsstd-reports.md2535
Runfile Liststd-runfile-list.md1125
Runfile Reportstd-runfile-report.md2839
Sitestd-site.md59
Tablesstd-tables.md618
UIstd-ui.md13
Upload Runsstd-upload-runs.md715
User Managementstd-user-management.md1636
User Settingsstd-user-settings.md38

Note: Introduction (SRS) and Known Issues are meta-documents with no testable requirements.

4.3 Rule STDs

Test specifications for analytical rule requirements (61 documents in rules/). Each rule STD contains decision tables with test vectors covering all input combinations.

See unified-coverage-report.md for the complete rule STD listing with coverage metrics.


5. Test Methods

The STD uses four test methods, selected per the Test Plan:

MethodCodeDescriptionWhen Used
API TestingTM-APIBackend API calls via PHPUnit/BehatPure backend logic, rules, data operations
UI TestingTM-UIBrowser automation via Behat/Mink + headless Chrome (CDP)User-facing features, form interactions
Hybrid TestingTM-HYBCombined API setup + UI verificationWorkflows spanning backend and frontend
Manual TestingTM-MANHuman verificationVisual/UX validation, edge cases

6. Relationship to Other Documents

Document SetLocationRelationship
SRSdocs/*.md, docs/rules/*.mdRequirements that tests validate
SDSdocs/sds/Design decisions informing test approach

Boundary with SDS

ContentLocation
How tests are structured (infrastructure)SDS
What tests exist and how to run themSTD (this document set)
HTML testability attributesSTD (std-ui-testability.md)

7. Version History

VersionDateDescription
3.0.0January 2026Complete STD with 100% requirement coverage