---
title: "Open a record whose route label needs encoding"
description: "Verify navigation to a test record with spaces, punctuation, and Unicode resolves the intended identifier without truncating or misparsing the route."
canonical_url: "https://vostride.com/agent-library/navigation-routing/encoded-route-identifier.md"
md_url: "https://vostride.com/agent-library/navigation-routing/encoded-route-identifier.md"
content_kind: "recipe"
topic: "navigation-routing"
---

# Open a record whose route label needs encoding

Verify navigation to a test record with spaces, punctuation, and Unicode resolves the intended identifier without truncating or misparsing the route.

## Risk

Display labels used in URLs can accidentally introduce path separators or query syntax. Test the product route builder through the UI and compare immutable identity instead of manually guessing its encoding scheme.

## Fixtures

- A test collection contains a record titled QA notes: café / east and a near-match record titled QA notes café.
- The fixture manifest records different immutable keys and distinctive body text for the two records.
- The product supports these titles and provides normal record links from the collection list.

## Steps

1. Open the collection and verify both fixture titles are visible and distinguishable.
2. Open QA notes: café / east using its application-generated link.
3. Verify the detail displays the exact intended title, its immutable key, and the east-only fixture body.
4. Reload the generated destination and verify the same record resolves without a route error or truncated title.
5. Return to the list, open the near-match record, and verify its different key, demonstrating the two links remain distinct.

## Expected results

- The application-generated route resolves the punctuation-bearing record key exactly.
- Reloading the destination preserves the same record identity despite encoded characters.
- The near-match title leads to its own distinct record rather than colliding with the first route.

## False-pass traps

- A normalized-looking title can hide a wrong record; compare the independent key and body.
- Constructing an unverified URL encoding by hand tests the test author's guess rather than the product link builder.

## Cleanup

- Delete both title-encoding fixtures from the test collection.

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