---
title: "Open the exact entity named by a notification"
description: "Verify an in-app notification deep link resolves to its referenced record, including workspace context and a distinguishing immutable identifier."
canonical_url: "https://vostride.com/agent-library/notifications/deep-link-target-identity.md"
md_url: "https://vostride.com/agent-library/notifications/deep-link-target-identity.md"
content_kind: "recipe"
topic: "notifications"
---

# Open the exact entity named by a notification

Verify an in-app notification deep link resolves to its referenced record, including workspace context and a distinguishing immutable identifier.

## Risk

Similar names make notification links easy to misroute. A destination page that merely looks relevant is insufficient when multiple records share a title across projects.

## Fixtures

- Two test projects each contain a task named Review release, with distinct keys ALPHA-16 and BETA-27.
- A prepared notification references only the BETA-27 task and includes its project context.
- The QA account can access both projects, and the current page starts in the Alpha project.

## Steps

1. Open the notification inbox from Alpha and locate the prepared review notification by its fixture marker.
2. Verify the notification summary identifies the Beta project before opening it.
3. Open the notification and verify the destination task key is BETA-27 with Beta project context.
4. Verify the task body contains the Beta-only fixture sentence and the unrelated Alpha key is not the active record.
5. Reload the destination and verify it still resolves to BETA-27, then return to the inbox and verify the notification state follows the documented read behavior.

## Expected results

- The deep link opens the exact referenced task identifier from the independent fixture manifest.
- The application switches project context consistently with the linked record.
- The Beta-specific body and persistent URL destination corroborate identity independently of the shared title.

## False-pass traps

- A matching Review release heading cannot distinguish the two fixture tasks.
- Manually searching for Beta after an incorrect link would conceal the routing failure.

## Cleanup

- Delete the prepared notification and both test tasks, leaving unrelated project data untouched.

## 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)

- [Notification QA recipes](/agent-library/notifications.md)
- [Software factory QA library](/agent-library.md)