QAVE Studio Docs
QAVE Studio Docs
Sign inGet started — the Studio loop
Getting StartedFirst assurance runQuick assure
ConceptsLifecycleGlossaryHow QAVE Studio worksComing soon
Account & workspaceSignup and loginPeopleDemo creditsRolesSettings
Generate simulation suitesContext templatePII and field enhanceDimensionsAgents and plannerDraft review and Save
ExportExport formatsExport formats (detail)
Assurance SDKSDK overviewQAVE Studio suite fetch APIAgent and JSONL queueLangfuse bridge
Execute and tracesRecipe chatbot (reference SUT)TracingFetch tracing
AssureEvaluate APIRubrics and evidenceReading scores
History
WorkbenchGolden data
CoverageCoverage dashboardCoverage strategiesCoverage advisorTest case quality
RAG AssuranceRAG runsRAG datasetsRAG analytics
Project evalsError analysisUnderstanding scores
Studio guidesDimensionsTuplesConversation modesMulti-lingual testingWorkflowsHuman reviewBest practices
ReferenceAPI and packagesTroubleshooting
Generate

Generate simulation suites

Context template through draft review to an approved suite — the Generation pipeline.

Generation turns a structured description of your AI system into an approved simulation suite ready for export and assurance.

Canonical flow

Context Template (form + optional attachments + optional dim upload)
  → PII (off by default; when on → scrub + human review)
  → Sync field enhance → store enhanced_fields (UI still shows original fields)
  → Generate Dimensions (manual)
  → Hub: Predefined Agents and/or Project Dimensions
  → Generate draft cases (agent stubs ∪ AI planner)
  → Draft review (edit / add / select) → Save (new suite or merge)
  → Suite is APPROVED at Save
  → Export / SDK / assure (downstream)

Product rules

  • Planner uses selected dimensions only; every planner case includes all selected dims.
  • Predefined Agents are not planner inputs; suites are the union of agent cases + planner cases.
  • Suite destination is chosen after draft review.
  • Pairwise / n-wise / Focus Areas / Tuples are not the primary product path. Setup Wizard in Studio is the guided UI for this pipeline.
  • Mark approve on suites is not required — suites are auto-APPROVED at Save.

Guides in this section

  1. Context template
  2. PII and field enhance
  3. Dimensions
  4. Agents and planner
  5. Draft review and Save

Settings

Project and organisation settings customers use in Studio.

Context template

Capture the system-under-test context that drives dimensions and planning.

On this page

Canonical flowProduct rulesGuides in this section