Async test waits: 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 wait and helper behavior. Compare awaited completion, bounded polling and deterministic fake timers with arbitrary real sleeps, keeping deliberate latency simulations separate.
The location and purpose of a delay matter. A sleep after starting an operation guesses when it will finish; a fake-service delay may deliberately keep an interface in its loading state.
Condition describes the observed waiting mechanism. It does not prove that an assertion targets the right event, that a timeout is appropriate, or that the suite will never be flaky.
This original code-reading exercise adapts a rule in the jev-lint repository linked by the cited X post. Snippets, labels and missing-context handling are authored for this page. It does not execute code, reproduce a repository scan or certify an application as safe.

Use the sample to understand the rule, then test your own input for async test waits.

Review the wait and helper behavior.

Open the decision rules and keep the intended distinction between Condition, Sleep, Simulation, Unclear. 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 Unclear before using a result. The label is a decision about the supplied information, not an executed action.
| Original input | Observed label | Leading probability |
|---|---|---|
| Wait and hope | Sleep | 99.0% |
| Await completion | Condition | 100% |
| Observed result | Condition | 100% |
| Fake latency | Simulation | 99.0% |
| Virtual timer | Condition | 100% |
| Opaque wait | Unclear | 75.0% |
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.
No. Delays can be intentional inputs, such as a slow fake service. Show where the delay occurs and what the test is trying to observe.
No. It makes the clock deterministic; the assertions and simulated behavior still require review.
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.