Watch the explanation. Practice the skill.

Evaluation design and release gates

Set test requirements before deciding whether to release.

Visual lesson1:42

Captions appear here during playback.

Evaluation design and release gates

Set test requirements before deciding whether to release.

Download transcriptOpen video file

Source-based teaching example · Fictional data · Reviewed 2026-10-03. Microsoft Mark · locally synthesized. On a small screen, use fullscreen for diagram details or read the transcript.

Read the descriptive transcript

0:00 · What you will learn

Set test requirements before deciding whether to release.

What appears on screen

Set test requirements before deciding whether to release.

0:06 · The idea

Include routine cases, difficult cases and attacks. Name the failures that block release. Report results for important groups instead of relying only on one overall score.

What appears on screen

Include routine cases, difficult cases and attacks. Name the failures that block release. Report results for important groups instead of relying only on one overall score.

0:21 · One useful term

Priority slice. A defined group of test cases whose result matters separately.

What appears on screen

A defined group of test cases whose result matters separately.

0:30 · A worked example

The exercise’s 75-case search-and-answer suite checks leakage, citations, support and timing. Its release rule requires zero observed leakage in that suite. A strong average cannot cancel a failed critical check.

What appears on screen

The exercise’s 75-case search-and-answer suite checks leakage, citations, support and timing. Its release rule requires zero observed leakage in that suite. A strong average cannot cancel a failed critical check.

0:48 · Your turn to think

Can you delete failed cases to make the release score improve? Pause and decide before continuing.

What appears on screen

Can you delete failed cases to make the release score improve? Pause the video if you need more time.

1:05 · Why this answer works

No. Keep the evidence. Correct a genuinely wrong test only with a recorded reason and preserved history.

What appears on screen

No. Keep the evidence. Correct a genuinely wrong test only with a recorded reason and preserved history.

1:15 · Check 1

Set thresholds before testing.

What appears on screen

Set thresholds before testing.

1:20 · Check 2

Keep counts and missing cases visible.

What appears on screen

Keep counts and missing cases visible.

1:25 · Check 3

Apply critical rules separately.

What appears on screen

Apply critical rules separately.

1:30 · Now try a different case

Open the lesson and try its different practice case. Use every check in the full task. Watching alone does not mark the lesson complete.

What appears on screen

Open the lesson Try the new case Check and revise The full task and its requirements are in the linked lesson.

Watching explains the example. Complete the lesson practice to check what you can do. Explore all visual lessons →