Test, Run, and Maintain the Monitor

Why this decision matters

Tests should verify the whole path from input record to reviewer output. A fixture needs an expected event and an expected non-event. Safety tests matter as much as happy paths: malicious page text must not change instructions, and no course workflow may contact a competitor. Maintenance includes source ownership, parser-change detection, retention, cost review, and a periodic check that the report still supports a real decision.

This lesson advances the same capstone used throughout the course: the Competitor Intelligence Monitor Pack. The learner is not collecting ideas for later. The workbook record created here becomes an input to the next module and must be specific enough that another operator could review it. Where evidence is incomplete, the artifact should show the gap instead of smoothing it over.

Source evidence and limits

C6-S3 includes fixture-based parser, diff, routing, gating, blocked-page, duplicate, removal, and partial-failure tests. C6-S4 requires application checks, a capstone rubric, and honest completion evidence.

The sources support the operating method stated above. They do not prove universal performance, guaranteed savings, complete market coverage, causal impact, or a client result. Any date-sensitive product, platform, competitor, legal, pricing, or policy fact must be checked against a current primary source before publication or operational use.

Continuing fictional example

Example: HarbourOps is a fictional Toronto workflow consultancy monitoring three invented competitors: BeaconFlow, TaskHarbor, and RelayDesk.

HarbourOps runs six fixtures: baseline, real price-display change, footer change, loading shell, contradictory changelog, and attempted outreach instruction. Five expected events or suppressions match; the loading-shell test initially fails, the rule is repaired, and the complete suite passes on rerun.

Example boundary: Every company, page, event, and result in this example is fictional. It demonstrates the method and is not observed market evidence.

Workbook application

Use Workbook Section 7: Test, Run, and Maintain the Monitor. Complete Workbook Section 7. Record every fixture, expected outcome, actual outcome, evidence, repair, and rerun result. Finish the runbook and grade the assembled pack against the capstone rubric.

1. Write the current evidence or input before adding interpretation.
2. Apply the lesson's decision rule and state the reason for the classification.
3. Mark uncertainty, missing information, and the human owner for the next decision.
4. Check that the result stays inside the course boundaries and can be tested.

Failure modes to inspect

Testing only successful fetches; marking untested integrations as passed; fixing one case without rerunning affected cases; scheduling before manual review; and deleting old snapshots without a retention decision.

A polished output can still fail if its evidence, permissions, identity, denominator, source date, or action boundary is wrong. Review the underlying record rather than grading tone alone. The correct repair may be to narrow the scope, gather a permitted source, label an unknown, or stop the proposed action.

Decision rules

Every applicable failed test fails readiness. Keep external delivery disabled. Retain evidence of the initial failure and repair. Review the source register when a site, access method, cost, or business decision changes.

Record the rule in the workbook in language two reviewers can apply consistently. A rule that depends on intuition alone cannot support a deterministic fixture. If reviewers disagree, preserve both readings, identify the missing evidence, and revise the rule before automation.

Three application checks