Legacy documentation — AI Fusion 1.x / 2.x. This article describes AI Fusion versions 1.x and 2.x. For AI Fusion 3, see the current GenAI Data Fusion documentation.
Evaluating AI agents is not a one-time activity but a continuous lifecycle.
As prompts, models, data, and agentic flows evolve, organizations must repeatedly validate that AI responses remain accurate, relevant, and aligned with business expectations.
The AI Fusion Evaluation Framework supports the full lifecycle of designing, executing, and improving AI evaluations.
This lifecycle connects design-time testing, automated regression validation, and production feedback analysis.
The lifecycle typically follows five stages:
Each stage helps teams systematically improve AI quality over time.
Note: Screenshot needed: Open
/static/aifusion/evaluation. Capture the evaluation workspace showing the suite tree with at least one suite and test visible. Save asimages/evaluation_lifecycle_overview.png

The first step is defining test scenarios that represent realistic user interactions.
Test cases typically include:
Tests represent complete multi-turn conversations customer journeys
These test cases are organized into test suites, allowing teams to validate entire features or business processes.
Many AI agents rely on enterprise data. Reliable evaluation therefore requires consistent test data.
The framework supports Data snapshots of the associated data product (micro DB)
This guarantees that tests can be rerun over time with the same data conditions.
Once tests are defined, they can be executed against the AI agent.
During execution, the system simulates a real user interaction by sending the conversation prompts to the agent and collecting its responses.
Execution can occur in several modes:
Responses are evaluated using an LLM-as-a-Judge approach.
An LLM, used during the evaluation process, analyzes each response and scores it across multiple quality dimensions such as:
The evaluator produces both:
This enables evaluation based on semantic correctness rather than exact wording.
Evaluation results provide insights into AI behavior and quality.
Teams can analyze results at multiple levels:
Failures can be investigated to identify issues in prompts, tools, or agent flows.
Evaluation results drive improvements in AI systems.
Teams may improve quality by:
Updated systems can then be re-tested using the same evaluation suites, enabling reliable regression testing.
Real conversations captured from QA or production environments can be imported into the evaluation framework.
Imported conversations can be:
This creates a continuous feedback loop between production behavior and design-time testing.
Legacy documentation — AI Fusion 1.x / 2.x. This article describes AI Fusion versions 1.x and 2.x. For AI Fusion 3, see the current GenAI Data Fusion documentation.
Evaluating AI agents is not a one-time activity but a continuous lifecycle.
As prompts, models, data, and agentic flows evolve, organizations must repeatedly validate that AI responses remain accurate, relevant, and aligned with business expectations.
The AI Fusion Evaluation Framework supports the full lifecycle of designing, executing, and improving AI evaluations.
This lifecycle connects design-time testing, automated regression validation, and production feedback analysis.
The lifecycle typically follows five stages:
Each stage helps teams systematically improve AI quality over time.
Note: Screenshot needed: Open
/static/aifusion/evaluation. Capture the evaluation workspace showing the suite tree with at least one suite and test visible. Save asimages/evaluation_lifecycle_overview.png

The first step is defining test scenarios that represent realistic user interactions.
Test cases typically include:
Tests represent complete multi-turn conversations customer journeys
These test cases are organized into test suites, allowing teams to validate entire features or business processes.
Many AI agents rely on enterprise data. Reliable evaluation therefore requires consistent test data.
The framework supports Data snapshots of the associated data product (micro DB)
This guarantees that tests can be rerun over time with the same data conditions.
Once tests are defined, they can be executed against the AI agent.
During execution, the system simulates a real user interaction by sending the conversation prompts to the agent and collecting its responses.
Execution can occur in several modes:
Responses are evaluated using an LLM-as-a-Judge approach.
An LLM, used during the evaluation process, analyzes each response and scores it across multiple quality dimensions such as:
The evaluator produces both:
This enables evaluation based on semantic correctness rather than exact wording.
Evaluation results provide insights into AI behavior and quality.
Teams can analyze results at multiple levels:
Failures can be investigated to identify issues in prompts, tools, or agent flows.
Evaluation results drive improvements in AI systems.
Teams may improve quality by:
Updated systems can then be re-tested using the same evaluation suites, enabling reliable regression testing.
Real conversations captured from QA or production environments can be imported into the evaluation framework.
Imported conversations can be:
This creates a continuous feedback loop between production behavior and design-time testing.