Fabric IQ and Data Gen samples#49247
Draft
jpalvarezl wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request improves the Azure AI Agents Java SDK by enhancing the FabricIQ sample code, updating test coverage, and aligning configuration usage. The main focus is on making the FabricIQ samples more flexible and testable, ensuring consistent configuration, and enabling automated testing for these scenarios.
Enhancements to FabricIQ sample code:
FabricIQSync.javaandFabricIQAsync.javanow support a configurable user input via theFABRIC_IQ_USER_INPUTenvironment variable, defaulting to a sample prompt if not provided. The agent instructions and agent names have also been updated for clarity and consistency. [1] [2] [3] [4] [5] [6]Test improvements and automation:
FabricIQSamplesTests.javaare now enabled and fully implemented. They dynamically create and clean up agents, use recorded configurations for playback, and validate that responses are completed and contain expected output. Utility methods were added for agent creation, configuration, and response validation.Configuration alignment:
ClientTestBase.javanow uses theFOUNDRY_PROJECT_ENDPOINTconfiguration key instead ofAZURE_AGENTS_ENDPOINTfor consistency with other samples and environments.Asset tag updates:
assets.jsonfor bothazure-ai-agentsandazure-ai-projectsto point to the latest versions. [1] [2]