Test evidence & CI
Purpose
Section titled “Purpose”Handover deliverables lists test reports as an expected artifact. This page standardizes where evidence lives and which commands produce it, without storing secrets or transient output in git.
Automated tests (Frappe app)
Section titled “Automated tests (Frappe app)”Typical command (exact targets depend on your hooks.py test configuration):
# From Bench root, with site contextbench --site <site> run-tests --app leekimerpCapture for handover: stdout/stderr log, date, Bench/Frappe/ERPNext versions from bench version, and git SHA.
Documentation site CI
Section titled “Documentation site CI”The repository includes a workflow that builds the docs when docs/** changes (see .github/workflows/deploy-docs.yml in the repo root). Evidence: successful GitHub Actions run for the commit being handed over.
Org-standard matrix (docs CI)
Section titled “Org-standard matrix (docs CI)”| Item | Value / note |
|---|---|
| Workflow file | .github/workflows/deploy-docs.yml |
| Workflow name (Actions UI) | Docs — build (Cloudflare-ready) |
| Job id | build (single job) |
| Triggers | push / pull_request when docs/**, leekimerp/**/doctype/**/*.json, or this workflow changes; also workflow_dispatch |
| PR gate | Same workflow runs on PRs — a green run is the minimum merge signal for doc-only changes |
| Build artifact name | docs-dist-client (contents: docs/dist/client) |
| Artifact retention | GitHub repository/org default (often 90 days; confirm in Settings → Actions → General if your policy differs) |
| Cloudflare Pages | Step uses cloudflare/pages-action when secrets are configured — production URL is org-specific |
Adjust the retention column in your runbook if the org pins a non-default retention policy.
What to archive
Section titled “What to archive”| Artifact | Format | Notes |
|---|---|---|
| Unit / integration log | Text or PDF export from CI | Redact connection strings |
| Coverage (if enabled) | HTML or CI summary | Optional |
| Manual smoke test | Short checklist | Login, create doc, integration ping in UAT |
Linking evidence in your org
Section titled “Linking evidence in your org”- Attach CI run URLs to your ticket or handover folder.
- Do not embed production database dumps in documentation.