chore(atomic): E2E tests for analytics triggered actions for Search Agent#7899
Merged
Conversation
…quent test navigations in the describe block
Co-authored-by: SimonMilord <73316533+SimonMilord@users.noreply.github.com>
erocheleau
reviewed
Jul 6, 2026
erocheleau
left a comment
Collaborator
There was a problem hiding this comment.
Not entirely sure I understand what's going on with the global variable for the answerIdSequence.
Could you explain a bit more what you're trying to do please?
erocheleau
approved these changes
Jul 6, 2026
erocheleau
left a comment
Collaborator
There was a problem hiding this comment.
I think it looks good now
erocheleau
approved these changes
Jul 6, 2026
alexprudhomme
approved these changes
Jul 6, 2026
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.
SFINT-6840
Added checks for analytics for the interactions in the search agent.
Also added a test to check the following:
After generating the 3rd answer, come back and interact with the 2nd answer and test these interactions:
To make sure analytics are sending the answerId of the given answer and not always the head answer.