Quality You Can Prove. Where quality intent and operational reality are always comparable, traceable, and provable.
In software development, a requirements document defines what the system is supposed to do. It describes intent, not what actually happens during execution.
In Qualityfolio, test artifacts written as code play the same role—they define what quality, compliance, security, and behavior are expected of a system.
Observed Results represent runtime reality—what we can actually see when tests are executed and evidence is collected.
A test artifact says: "This behavior must be verified."
Execution either produces valid evidence—or it does not.
A single, structured file that captures quality intent in a strict, machine-readable hierarchy.
The system or product under test
The testing and assurance approach
Scope, objectives, and coverage intent
Logical grouping of related tests
Specific, verifiable expectation
Proof produced when test is executed
This hierarchy is explicit, inspectable, and machine-readable.
Nothing is implicit. Nothing is external. All intent, execution, and proof live in the artifact.
They are the source of Expected Tests—declarations of quality intent.
Execution details, results, and artifacts are captured as structured evidence.
Recorded inside YAML blocks at the evidence level, preserving historical execution truth without duplicating tests.
Introduced by overriding the plan or suite, allowing a single requirement to govern multiple test cases.
Declared at the evidence level, directly tied to the observed outcome that triggered them.
Operational Truth is not reconstructed after the fact. It is encoded directly into the test artifacts themselves.
Operational Truth emerges only when every test case has evidence and every piece of evidence maps back to a test case.
If a test case exists but no corresponding evidence block exists, the system's quality intent was defined but never proven.
Execution Failure
Pipelines did not run or environments were unavailable
Process Failure
Test was skipped, forgotten, or manually bypassed
Compliance Failure
Required control declared but never validated
Qualityfolio treats this as an unverified expectation—not a passed test.
If evidence exists without a corresponding test case, it means execution occurred without declared intent—a governance failure.
Behavior Never Defined
The test case was never formally declared
Cannot Be Traced
Cannot be mapped to requirements or plans
Not Defensible
Creates false confidence or audit noise
If execution is not declared as a test case, it is not trusted as proof.
Quality is provable and auditable
Assurance is incomplete
Governance is broken
Just as modern engineering rejects undocumented code in production, Qualityfolio rejects:
Operational Truth is not a report. It is a continuously validated state.