Test case generation

Dezycro generates test cases from your feature's TRD using LogicStudio — an interactive interface for reviewing, toggling, and finalizing AI-generated tests.

The output of LogicStudio becomes the feature's journeys — see The Workbook → Journeys.

Opening LogicStudio

Navigate to a feature and open the Validation tab in the feature stepper.

The Generate Validation Cases button kicks off LogicStudio's generation workflow. The first time you open this tab for a feature you'll see this empty state; once cases exist they appear as a grid in the same panel.

Generating test cases

1. Click Generate in LogicStudio.
2. The AI analyzes your feature's TRD + any ingested documents.
3. Test cases are generated covering:
4. Happy paths — standard user flows
5. Edge cases — boundary conditions, unusual inputs
6. Negative testing — invalid inputs, unauthorized access, error handling
7. Integration points — interactions between features

Info

Generation runs as a Temporal workflow and may take 1-3 minutes for a large TRD. A progress indicator shows the current phase. You can navigate away and come back; status is preserved server-side.

You can also generate via the MCP server: mcp__dezycro__generate_tests(workspaceId, featureId, docId) then poll generation_status until COMPLETED.

Reviewing test cases

Generated test cases appear in a validation grid. Each test case includes:

Field	Description
Name	A concise description of what the test verifies
Description	Detailed test scenario and steps
Linked intent	The TRD/PRD statement this test is grounded in
Status	Active, Inactive, Draft, or Archived

Toggling tests

• Active — included in verifier runs
• Inactive — excluded but preserved for later

Use Select All / Deselect All for bulk operations. Toggling is non-destructive — you can re-activate any test at any time.

Enforcement

Each journey has an enforcement state:

• ENFORCED — failure blocks the feature lifecycle from advancing to VERIFIED
• OBSERVED — logged but non-blocking (useful for nice-to-have coverage or in-progress journeys)

Set via the journey details panel.

Finalizing

When you're satisfied with the test selection, click Finalize. This:

• Marks the selected tests as Active
• Triggers JEP (verifier binary) generation
• Returns control to the feature page

You can also Continue Later to come back without finalizing.

Auto-baseline promotion

The first time a journey passes the verifier, its observed response shape is captured as a baseline. Subsequent runs assert against that baseline.

If a journey's contract changes intentionally (e.g. you added a field), promote the new run to the new baseline via Promote to baseline in the journey details. Stale baselines (older than staleBaselineDays, default 14) surface in the coverage report.

Promotion to regression suite

Journeys that have passed N consecutive verifier runs are eligible for promotion to regression — moves them into a "must always pass" set that runs on every CI build. Configure the threshold under workspace settings.