Unit test concept review: six recorded examples
The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.
Review the test name, setup, action and assertions. Distinguish one coherent outcome from unrelated checks or obscured intent; several related assertions do not automatically make a test too broad.
A test can need several assertions to explain one result. Checking the fields of a receipt is different from testing account arithmetic and email rendering in the same function.
The label is a reading aid for review. It does not say the assertions pass, the implementation is correct or the suite covers every requirement.
The source clean-code reviewer includes a test-concept question. These original inputs make the difference between a behavioral concept and an assertion count explicit.
This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Use the sample to understand the rule, then test your own input for unit test concept review.

Review the test name, setup, action and assertions.

Open the decision rules and keep the intended distinction between One behavior, Mixed behaviors, Obscured intent, Review. Edit the choices only when testing your own rule.

Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

Review Review before using a result. The label is a decision about the supplied information, not an executed action.
| Original input | Observed label | Leading probability |
|---|---|---|
| Related output fields | One behavior | 100% |
| Two independent jobs | Mixed behaviors | 96.0% |
| Named table cases | One behavior | 100% |
| Purpose lost in setup | Obscured intent | 69.0% |
| Missing helper contract | Review | 76.0% |
| One state transition | One behavior | 100% |
These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified
The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.
The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json
# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.The input contract and these limits define what the result means.
Not necessarily. Several checks can describe one outcome. This example looks at their purpose rather than their number.
Having the code is different from being able to explain the scenario it checks. Unexplained aggregate assertions or unrelated setup can conceal that purpose.
It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.
No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.
Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.