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
Coverage

Coverage

Measure release readiness from dimensions, tuples, and approved suites.

Coverage answers: have we tested what matters for this system? Metrics come from approved dimensions, tuples, and test cases — not from uploaded files alone.

Open Coverage in Studio (/coverage).

Guides

GuideUse when
Coverage dashboardScorecard, readiness score, gaps, attestation
Coverage strategiesPairwise, N-wise, full Cartesian
Coverage advisorDomain taxonomy gaps on the scorecard
Test case qualityQuality rubrics and improving cases

Related

  • Dimensions
  • Generate

Golden data

How SME annotations become calibration and preference pairs.

Coverage dashboard

Coverage dashboard

On this page

GuidesRelated