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
Export

Export

Download approved suites for offline runners, CI, and assurance tooling.

Exports are the primary offline handoff from Generation to execution and assurance tooling.

How to export

  1. Ensure the suite is APPROVED (Generation Save already does this).
  2. Open Exports.
  3. Select one or more suites (or all approved).
  4. Choose a format and trigger the export.
  5. Download when the job completes.

APIs

POST /projects/{id}/exports/trigger
POST /projects/{id}/test-suites/{suite_id}/exports/trigger
POST /workflows/export-dataset

See formats.

Draft review and Save

Edit and select drafts, then save a new approved suite or merge into an existing one.

Export formats

JSONL, Simulator JSONL, Pytest, Excel, and Editable JSON contracts.

On this page

How to exportAPIs