Test Matrices, Artifacts, and Failure Diagnostics Artifacts should help diagnose failed or expensive jobs, not become an uncontrolled data dump. Upload browser traces, coverage, release manifests, or test reports with explicit retention. Matrix jobs are useful when the same contract genuinely needs multiple environments; do not multiply cost without a compatibility requirement.
Engineer Job fails → Collect report → Upload artifact → inspects
What this changes in TaskFlow • Upload useful diagnostics
• Set retention deliberately
• Do not upload secrets or .env files
• Use matrices for real compatibility coverage
actions/upload-artifact current v7 line stores diagnostic/release files; never upload secrets.
Tests are executable behavioral contracts. Good tests protect meaningful invariants and failure cases, not implementation trivia.
Restate the goal of “Test Matrices Artifacts and Failure Diagnostics” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: behavior contract → arrange → act → assert → regression signal. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: .github/workflows/ci.yml plus release/deploy workflows that build once, tag by commit SHA, and gate promotion.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
it("rejects deleting another member's task", async () => {
const response = await asUser(bob).delete(`/tasks/${aliceTask.id}`);
expect(response.status).toBe(403);
expect(await taskStillExists(aliceTask.id)).toBe(true);
});Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Look for shared database state, timers, globals, unordered execution, or missing cleanup before adding retries.
Move the highest-risk boundary to an integration test with the real adapter/database.
Without copying the final source, create a second small scenario that applies “Test Matrices Artifacts and Failure Diagnostics” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Add environment protection/permissions for deployment and ensure stale production runs are not silently canceled mid-release.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Broad write permissions for all jobs
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.