---
title: "Mention the intended teammate with a shared display name"
description: "Verify that a mention picker distinguishes two test teammates with identical names and stores the intended recipient identity in a synthetic comment."
canonical_url: "https://vostride.com/agent-library/collaboration/mention-picker-disambiguation.md"
md_url: "https://vostride.com/agent-library/collaboration/mention-picker-disambiguation.md"
content_kind: "recipe"
topic: "collaboration"
---

# Mention the intended teammate with a shared display name

Verify that a mention picker distinguishes two test teammates with identical names and stores the intended recipient identity in a synthetic comment.

## Risk

A visually correct mention can resolve to the wrong account when display names collide. Use test-only identities and a non-delivering workspace so the workflow cannot notify real people.

## Fixtures

- Two fixture members both display Alex Lee but have distinguishable usernames alex.design and alex.engineering.
- A disposable issue permits comments, and outbound delivery is routed only to fixture inboxes.
- The intended recipient is alex.engineering, with its immutable member identifier recorded independently.

## Steps

1. Open the issue comment composer and type a mention query for Alex Lee.
2. Verify both matching members appear with distinguishing secondary labels before choosing alex.engineering.
3. Complete the comment with the unique phrase QA mention target and submit it once.
4. Verify the rendered comment contains the mention and the fixture phrase, then open the mention profile if supported to verify the engineering username.
5. Run the prepared comment-recipient check and verify the stored mention identifier is the engineering fixture member and excludes the design member.

## Expected results

- The mention picker supplies enough visible context to select the intended same-name account.
- The saved comment references the independently recorded engineering member identifier.
- No mention event targets the design fixture member for this comment.

## False-pass traps

- The rendered Alex Lee text alone cannot establish recipient identity.
- Typing a plain at-sign and name without selecting a mention may create ordinary text rather than a stored mention.

## Cleanup

- Delete the synthetic comment and any resulting fixture inbox events.

## Use with agent-qa

Adapt this test design to your application's acceptance criteria and configured target using the [recipe execution guide](/agent-library/software-factory/turn-a-recipe-into-an-agent-qa-test.md). External fixture setup and non-UI checks require your own supported hooks or test tooling. Validate the authored test, execute it, and inspect the completed evidence; this recipe is not a recorded test result.

## References

- [agent-qa test](/docs/agent-qa/configuration/test.md)
- [agent-qa first test](/docs/agent-qa/guides/first-test.md)
- [agent-qa web testing](/docs/agent-qa/guides/web-testing.md)

- [Collaboration QA recipes](/agent-library/collaboration.md)
- [Software factory QA library](/agent-library.md)