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
Execute & Traces

Execute and traces

Drive the system under test and capture traces for assurance.

Execution produces the conversations or agent trajectories that assurance scores. Tracing captures the evidence; fetch normalizes it into one schema.

In this section

PageUse when
Recipe chatbot SUTLocal reference bot for tutorials
TracingLangfuse-centric capture today
Fetch tracingNormalize traces into the assure schema

Modes

  • Active drive — platform/SDK sends messages or tool calls to the SUT
  • Trace-only — SUT already runs in production; skip drive and proceed to fetch

Langfuse bridge

Fetch SUT traces from Langfuse, normalize, and submit to the assure Gateway.

Recipe chatbot (reference SUT)

Use the recipe-chatbot HTTP API as the canonical system under test for tutorials.

On this page

In this sectionModes