Help Center
Browse articles in this category, or use search to jump to a specific task.
11 articles.
Rule Intelligence turns requirement documents and API specs into structured, testable requirements—review them, then feed them into test generation with coverage and traceability.
Upload requirement documents, extract text, AI-parse them into typed requirements, then review, edit, and approve the requirements that drive test generation.
Upload sample Excel/CSV data so generated tests use realistic inputs, then check generation readiness per endpoint and tune request/response mapping overrides.
The Coverage tab shows a per-endpoint × strategy test-coverage matrix, flags endpoints with no tests, and reports how faithfully requirements were extracted from your documents.
Trace each requirement to the tests and endpoints that verify it, run impact analysis when requirements change, and export a requirements traceability matrix for audits.
The Learning tab shows what your workspace has learned from reviewer edits and test runs—acceptance rate, edit distance, time to green, flake rate, and a generation-quality score.
Most projects are described by more than one document: a BRD, a rules workbook, a set of user stories, meeting notes, an email thread.
When several documents describe the same system, they overlap. The BRD says "Email is required", the meeting notes say "Customer email must be present", and the rules workbook lists it again as BR-007.
A requirements workbook is rarely one table. A typical file has a cover sheet, a list of numbered requirements under a two-row title, a data dictionary of fields, a sheet of test data, and a glossary.
Requirement documents change. When the BRD moves from v1 to v2, you need to know which rules changed, which are new, and which disappeared — without reviewing all of them again and without losing the tests you already built.
Every other requirements screen reports what Shift-Left Studio found. The Gaps & conflicts tab reports what it could not turn into a test, and why.
