How It Works

From Markdown to Measured Confidence

Step 1

Author

Write test cases in Markdown with setup, action, and expectation sections.

Step 2

Execute

Run tests via the CLI or CI runner. Markdown cells become executable tests.

Step 3

Capture

Results, logs, and metrics are automatically recorded during execution.

Step 4

Store

Structured results saved in local or remote SQL databases with full provenance.

Step 5

Visualize

Results appear in dashboards, Markdown summaries, or compliance exports.

Typical Test Structure

Qualityfolio organizes test artifacts using a flexible, six-level heading hierarchy—Project → Strategy → Test Plan → Test Suite → Test Case → Evidence. The hierarchy is optional and extensible, allowing teams to introduce Requirements, Test Cycles, and Issues as additional sections by overriding heading depth levels within the same test artifact file. This design enables end-to-end traceability across planning, execution, defects, and supporting evidence without enforcing a rigid structure.

plaintext

ASSURANCE-PRIME/
├── support/
│   └── assurance/
│       └── qualityfolio/
│           ├── evidence/
│           │   ├── TC-GLUE-001/
│           │   │   └── 1.1/
│           │   │       ├── result.auto.json
│           │   │       └── run.auto.md
│           │   └── TC-GLUE-002/
│           │       └── 1.1/
│           │           ├── loginButtonClick.png
│           │           ├── result.auto.json
│           │           └── run.auto.md
│           ├── sqlpage/
│           │   └── sqlpage.json                  # runtime configuration file for SQLPage, auto-generated
│           ├── test-artifacts/
│           │   └── example-artifact.md
│           ├── qualityfolio-json-etl.sql         # SQL ETL script for Qualityfolio data
│           ├── qualityfolio.md                   # SQLPage Markdown page (DB config + queries)
│           └── resource-surveillance.sqlite.db   # Database generated