Test state isolation: six recorded examples
The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.
Show the tests, fixture mutations and reset lifecycle. Distinguish cross-test dependencies from fresh or completely reset state, with read-only sharing considered separately.
Isolation is about starting conditions. A file-level fixture can be harmless when read-only, while a later test can depend on another test even if the runner promises a fixed order.
This example reads supplied lifecycle evidence. It does not run tests in shuffled order or prove that a database, browser context or remote service has been reset.
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 test state isolation.

Show the tests, fixture mutations and reset lifecycle.

Open the decision rules and keep the intended distinction between Dependent, Isolated, Readonly, 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 |
|---|---|---|
| Earlier test supplies data | Dependent | 99.0% |
| Reset for each test | Isolated | 81.0% |
| Shared constants | Readonly | 100% |
| Local setup | Isolated | 97.0% |
| Serial dependency | Dependent | 100% |
| Reset helper unknown | Unclear | 88.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. It may make a dependency repeatable while retaining it. This rule asks whether a case can start without another case’s leftovers.
A connection object alone does not decide the result. Supply whether the tests mutate shared records and how those records are reset.
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.