write-tc

Converting scenario narratives into structured test cases is done by transforming the text into a JSON TC schema with fields like id, priority, and expected results. You provide the scenario narrative, and the system generates the structured test-case JSON file automatically.

The test-case JSON schema enforces specific metadata fields including id, depth_1 through depth_6, priority, expected, and note. This structured format ensures consistent test case creation and preserves IDs during subsequent edits.

Yes, you can reference Confluence Page IDs or Figma node IDs to connect and manage test cases. This anchors the generated TC JSON files to the original design specs and scenario sources for traceable QA workflows.

Maintaining test case IDs during edits is handled natively by preserving the id field within the JSON TC schema. The system enforces this schema structure to ensure existing identifiers remain intact while updating other metadata fields like priority or expected results.

Test case generation applies to QA workflows across Confluence-based planning, design specs, and scenario sources. It systematically reduces manual effort by converting narrative scenarios from these various platforms into reproducible JSON test cases.

Structuring depth and priority in test case JSON is enforced through the schema's depth_1 through depth_6 hierarchy and a dedicated priority field. The system automatically maps narrative scenarios to these layered metadata fields for consistent quality verification.