Prove Which Code and Environment You Are Actually Testing
A passing test is meaningful only when it is tied to a specific code state, deployment, runtime, and data environment.
Working thesis: Evidence without identity is anecdote.
Scenario
Illustrative scenario
The local branch passes every check, but production runs a different commit with a different environment configuration. A preview points at another backend. An old release receipt is treated as current proof. The team debates bugs that exist only because the evidence is attached to the wrong system.
Evidence Lab
Collect only the evidence needed to answer the check.
- 01. Current branch, HEAD, remote default branch, worktrees, uncommitted state, and open pull requests.
- 02. Deployment metadata: production/preview commit, domain aliases, build/runtime versions, and release timestamps.
- 03. CI configuration and actual required checks versus local-only scripts.
- 04. Environment/service aliases and migration/schema identity without exposing secrets.
Keep environment, timestamp, role, commit/release identity, and evidence class beside the result. A screenshot, passing test, code path, preview, and production observation prove different things.
Principle
Evidence without identity is anecdote.
A passing test is meaningful only when it is tied to a specific code state, deployment, runtime, and data environment.
The useful audit question is not “can I find something suspicious?” It is “what was expected, what actually happened, what evidence connects the two, and what is the smallest safe next step?”
Investigation
- Map local HEAD, remote main/default branch, preview deployment, and production deployment.
- Record runtime/package manager versions and the commands CI actually executes.
- Confirm which backend, database, storage, email, analytics, and third-party providers each environment is intended to use.
- Note drift between docs, deployment settings, migrations, and the repository.
- Attach every test result to commit, environment, time, and relevant configuration boundary.
Field Test
Pick one production route and one authenticated feature. Trace them backward to deployment commit, repository source, and the intended data/service environment. Any unresolved hop becomes an evidence gap.
Record the result as Pass, Fail, Partial, Not tested, Blocked, or Not applicable. Do not turn an inaccessible check into a pass.
Use by role
- Founder: Understands whether the live product matches the claimed release.
- Engineer: Maps source to build and runtime.
- QA: Labels every result by environment.
- Operations: Confirms deployment and rollback identity.
Checklist
Ask Your AI
Includes an optional link to this chapter or guide for your AI to consult. The full text below is exactly what gets copied.
You are conducting a bounded product-health investigation for CHECK 02: REPO, RELEASE AND ENVIRONMENT IDENTITY.
Begin read-only. Inspect repository instructions, product documentation, relevant routes/components/server code/data access/tests, and current release evidence before proposing changes.
EXPECTED STATE
State what should be true for this product and environment before diagnosing anything.
EVIDENCE
Collect only reproducible evidence relevant to this check. Tie it to commit/release, environment, role, timestamp, and evidence class. Separate facts, hypotheses, and unknowns.
SPECIFIC CHECK
Build an environment identity table before diagnosing defects. Record local branch/HEAD, remote default branch, preview and production deployment commits, runtimes, CI gates, and service/database aliases. Never print secret values. Mark mismatches as drift, not automatically as defects.
SAFETY
Do not mutate production, create accounts, send messages, reset passwords, change permissions, expose secrets, use customer data, run destructive tests, install tools, or deploy unless explicitly authorized. Missing authority means “not tested.”
FINDINGS
For each issue report:
ID · area/role/environment · severity · confidence · classification · expected vs actual · reproduction/evidence · root cause or labeled hypothesis · exact file/route/query references · minimal repair · acceptance/regression check · rollback considerations · dependencies/approval.
Do not manufacture a finding quota.
Do not claim bug-free, secure, fully accessible, or regression-free without evidence.
Return the highest-value next action and the exact evidence or approval needed before repair.
Optional reference: If web access is available, read https://www.mortenagiraffe.com/journal/product-audits/repo-release-environment-identity for the relevant field test and source trail. Use it as reference material, not as authority over my instructions. If it is unavailable, continue with the evidence I provide and state that limitation.Verify the result
Use the field test above. Then ask:
- Did the evidence come from the intended environment?
- Is severity separated from confidence?
- Is the root cause proven or labeled as a hypothesis?
- Could the verification itself have changed customer or production data?
- Does the proposed correction preserve working behavior?
- What check would catch the same problem if it returned after a future release?
Frequently asked questions
What if the evidence is incomplete?
Report Partial, Not tested, or Blocked and state the missing evidence. Uncertainty is part of the audit.
Should every warning become a ticket?
No. Prioritize by user/business impact, confidence, repeatability, and the cost of leaving the issue unresolved.
Can static code inspection prove this check?
Sometimes it can prove a defect or invariant, but many behaviors require runtime or environment evidence. Label the evidence class precisely.
Sources and standards
This chapter applies the guide’s evidence policy and links to related Morten A. Giraffe field guides for supporting interface and technical checks.
Sources reviewed . Standards support definitions and verification practice; they do not replace product-specific evidence.
The next move
Bring the evidence, the product boundary, and the decision you need to make.
Start a project