Vansah Intelligence (AI) uses Large Language Models (LLMs) to generate Test Cases based only on the information the user provides. It does not access Jira credentials, secrets, or unrelated data.
What the AI uses as context
The Jira Work Item: Summary, Description
Optional Fields: Jira Custom Fields, Components, Labels, Priority
Your conventions: Step style (Gherkin vs procedural)
The generation workflow
Trigger
From a Jira Work Item (Story/Epic/Bug), click Generate Tests with Vansah AI (or use the API).Coverage controls
Choose scope: Test Case Type: Happy path, Negative/Edge cases, Boundary & data‑driven, Non‑functional (perf/security/accessibility placeholders).Draft creation
Vansah Intelligence (LLM‑powered) produces:Test title & objective
Preconditions & required data
Step‑by‑step actions with verifiable expected results
Trace links: acceptance‑criteria → step mapping
Suggested labels/components/folder placement
Human‑in‑the‑loop review
Inline edit, accept/reject individual steps, request “Regenerate step(s)” or “Expand edge cases”.Save & link
On save, Vansah:Creates Jira‑native test(s)
Auto‑links them to the requirement (traceability)
Records provenance (generated‑by‑AI, source issue, timestamp)
Quality guardrails
Policy checks (required fields, naming, step length, data placeholders)
What the AI actually outputs (example)
Title: “Checkout - Apply percentage discount with expired promo (negative)”
Objective: Validate rejection of expired promo codes at payment.
Preconditions: Shopper account exists; cart has ≥1 item; expired promo “SAVE10” (expired 30‑Jun‑2025).
Steps & Expected Results (abbrev.)
Open cart → Cart items visible; totals shown.
Enter code “SAVE10” → System displays ‘Promo expired’; discount not applied; totals unchanged.
Proceed to payment → No discount lines present.
Links: Story AC#3 “Invalid/expired promos must be rejected”.
Labels:
negative,payments,promo,boundary,P1.
Controls you can tune
Style: Gherkin vs step/expected; single‑case vs scenario outline.
Granularity: concise vs exhaustive; number of variants.
Type: Test Case Type functional/security/accessibility as per Vansah project configuration.
Data handling & residency (high level)
Context is minimised to what’s needed.
Region‑aligned processing and data‑residency options are supported (aligning with your Jira region).
Audit trail logs who generated what, and when.
API notes (for automation)
Endpoint to generate tests from an issue key (with options for coverage level, style, folder).
Endpoint to re‑prompt/expand negative or boundary cases.