---
title: "Follow a breadcrumb to the actual record parent"
description: "Verify breadcrumb links follow the stored hierarchy for a nested record instead of reusing a similarly named parent from previous navigation."
canonical_url: "https://vostride.com/agent-library/navigation-routing/breadcrumb-parent-identity.md"
md_url: "https://vostride.com/agent-library/navigation-routing/breadcrumb-parent-identity.md"
content_kind: "recipe"
topic: "navigation-routing"
---

# Follow a breadcrumb to the actual record parent

Verify breadcrumb links follow the stored hierarchy for a nested record instead of reusing a similarly named parent from previous navigation.

## Risk

Breadcrumbs can display a plausible parent label while carrying a stale link. Duplicate parent names across workspaces make immutable identity and distinguishing sibling content necessary.

## Fixtures

- Two test workspaces each contain a project called Launch plan with distinct project keys NORTH-8 and SOUTH-9.
- The child task BREAD-21 belongs only to SOUTH-9, whose sibling task is South checklist.
- The browser first visits NORTH-8 to exercise potential stale breadcrumb context before opening the child direct link.

## Steps

1. Open NORTH-8 and verify its workspace and project identifier.
2. Open the prepared direct link to BREAD-21 and verify its child key and South workspace context.
3. Inspect the project breadcrumb label, activate it, and verify the destination project key is SOUTH-9.
4. Verify South checklist appears in the project list and North-only fixture content is absent.
5. Use browser Back to return to BREAD-21 and verify the child still shows the correct hierarchy after the breadcrumb round trip.

## Expected results

- The breadcrumb destination equals the child's stored parent key from the independent fixture manifest.
- The South-only sibling corroborates the parent destination despite the shared project title.
- The earlier North visit does not leak its project link into the later child route.

## False-pass traps

- A Launch plan heading alone cannot distinguish the two parent records.
- Navigating through the global workspace selector instead of the breadcrumb would bypass its link binding.

## Cleanup

- Delete the two test projects and their child fixtures according to the test workspace cleanup policy.

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

- [Navigation and routing QA recipes](/agent-library/navigation-routing.md)
- [Software factory QA library](/agent-library.md)