Milestones & schedules

Verification happens over time, against deadlines and on a cadence. Milestones group runs toward a target, and schedules run a plan automatically on a recurring basis.

Milestones

A milestone is a verification target with a due date — a release candidate, a design review, a submission gate. You give it a name, a description, and a due date, then associate the relevant test runs with it. As those runs are executed, the milestone shows overall progress, so you can answer “are we ready for this gate?” from live results rather than a status meeting.

Because runs reference the milestone they belong to (see Runs & execution), a milestone is a real rollup of work, not a label — its progress reflects exactly what’s been verified and what hasn’t.

Schedules

A schedule runs a test plan on a recurring cadence without someone kicking off each pass by hand. You link the plan, set a frequency — daily, weekly, or monthly, with the day of the week or month where it applies — and assign who’s responsible. The schedule then generates runs on that cadence.

A scheduled run carries its own history: its next run and last run, and a pass rate trend across executions. This is how you keep a regression or nightly suite honest over a long program — verification keeps happening on rhythm, and a slipping pass rate is visible early.

Milestones, schedules, and runs together

The three fit together cleanly: a run is one execution, a schedule produces runs on a cadence, and a milestone groups runs toward a date. Used together, they turn a library of test cases into a managed verification program with both deadlines and a heartbeat.