test(v2): match Arabic inspector steps by configured inspector name#997
Merged
Conversation
…name
The backend uses the inspector's own name as the step agent id, and this
test names its inspector 'ArabicContentValidator-<model>', which the
substring matcher ('inspector') missed.
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
1 participant
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.
Follow-up to #996: the Arabic tests name their inspector
ArabicContentValidator-<model>, which doesn't contain the word "inspector", so the substring matcher missed the steps. Now also matches the step agent id against the configured inspector's name.Fixes
test_arabic_inspector_agent_across_llms[gpt-4o]and[gpt-4.1-nano](the[claude-opus-4.6]variant fails earlier on the empty-output backend issue).🤖 Generated with Claude Code
https://claude.ai/code/session_018dCb6BE5bqjCrmsiPDGLRr