Jev targeted test gap

Check whether tests assert the behavior that changed

Compare the change with supplied test paths and assertions. Identify a targeted assertion or a visible gap in the declared review set without inferring whole-repository coverage.

Is a targeted assertion present?Live API
Try an example

The test reaches the new branch and asserts its result.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

The API-collected roundup directly links Jev Review. A recorded HTTP redirect identifies the repository, and pinned source code defines this review decision. The six inputs and Choice outcomes are original adaptations; the upstream screening questions use Noul. This page does not run tests, inspect a repository or certify a release.

Compare changed behavior with supplied tests.

Decision rules and labels
Targeted assertion shownGap shownNo behavior changeNeed test evidence
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

Calling the changed function is not the same as checking its result.

The invocation-only preset reaches the empty-token branch but catches every exception without an assertion. It would not distinguish the required error from many incorrect outcomes. The positive preset asserts that the thrown error matches the required message.

The boundary example tests both the newly accepted value and the next rejected value. Those assertions concern the change itself; an unrelated passing test does not provide the same evidence.

Gap shown is limited to a test set explicitly marked complete for this review. An unknown excerpt receives Need test evidence. The window never executes tests, calculates coverage percentages or claims that the rest of a repository has no tests.

The API-collected roundup directly links Jev Review. A recorded HTTP redirect identifies the repository, and pinned source code defines this review decision. The six inputs and Choice outcomes are original adaptations; the upstream screening questions use Noul. This page does not run tests, inspect a repository or certify a release.

Illustration of checking a code change and reviewing a flagged line
Illustration of the decision flow.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for tests for changed behavior.

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Compare the change with supplied test paths and assertions.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between Targeted assertion shown, Gap shown, No behavior change, Need test evidence. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

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

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review Need test evidence before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Failure branch assertedTargeted assertion shown86.0%
Only success testedGap shown97.0%
Formatting onlyNo behavior change88.0%
Boundary assertedTargeted assertion shown93.0%
Invocation without assertionGap shown92.0%
Subset unknownGap shown62.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. 5 of 6 results matched the authored fixture expectations. For Subset unknown, the expectation was Need test evidence; the observed choice was Gap shown.Verified

Understand the results

Replay the saved synthetic requests to inspect each recorded decision

Replay the saved synthetic requests to inspect each recorded decision. Authored expectations and model disagreements remain available; these examples are not a production accuracy benchmark.

Using the result in your application

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.

Runnable offline example

Run one sample, then inspect the local packet

View the code example
Single-request replay
npm install @typesafe-ai/sdk@0.6.0
# Set TYPESAFE_API_KEY privately in your shell.
node run-choice-sample.mjs samples.json case-1
python preview_choice_workflow.py samples.json saved-api-results.json
Scope of this demo

Where this decision fits

Useful scope

  • Checking a new failure branch
  • Reviewing boundary assertions
  • Distinguishing invocation from verification

Outside this demonstration

  • Running the test suite
  • Measuring repository-wide coverage
  • Inferring missing tests from a partial excerpt
Example FAQ

Questions about targeted test gap.

Input scope and downstream handling determine what this judgment means.

Does a passing test prove the change is covered?

Only a relevant assertion can support that conclusion for the supplied behavior. A passing unrelated test says nothing about the changed branch.

Why supply test-set completeness?

Without it, a missing assertion may simply be outside the excerpt. The page keeps that uncertainty explicit.

Is the leading probability an accuracy measurement?

No. It is one value in the returned distribution over this request’s choices. The six synthetic fixtures have authored expectations; they do not measure production accuracy.

What happens on an API failure?

The window displays an error without a fresh judgment. An incomplete-input outcome describes the supplied evidence and is not used as a fallback for provider failure.

Try your own targeted test gap input

Edit the input above, or open the Playground to explore another decision.