---
title: "Verify right-to-left layouts preserve mixed identifiers"
description: "Test a right-to-left detail screen with Latin identifiers and numbers, checking readable ordering, correct navigation, and unchanged stored values."
canonical_url: "https://vostride.com/agent-library/localization/right-to-left-mixed-identifiers.md"
md_url: "https://vostride.com/agent-library/localization/right-to-left-mixed-identifiers.md"
content_kind: "recipe"
topic: "localization"
---

# Verify right-to-left layouts preserve mixed identifiers

Test a right-to-left detail screen with Latin identifiers and numbers, checking readable ordering, correct navigation, and unchanged stored values.

## Risk

Bidirectional text can visually reorder punctuation in an identifier even when the underlying value is intact. Verify both the displayed association and the exact stored identifier, with controls exercised to catch mirrored hit-target mistakes.

## Fixtures

- An owned sandbox application configured to a supported right-to-left locale through product settings or an external fixture.
- A test ticket with a localized title, Latin key QA-2048, and a mixed-direction reference containing digits and punctuation.
- A read-only ticket oracle and two neighboring records so previous and next navigation have distinct expected destinations.

## Steps

1. Open QA-2048 and verify its localized title is associated with the complete Latin key and mixed-direction reference without clipped characters.
2. Use the product next-record control according to its documented semantics and verify the destination identifier matches the expected neighboring record.
3. Return to QA-2048, edit only the localized title, and verify the key and reference remain unchanged in the editor.
4. Save and reopen the ticket; verify the new title is readable and the identifier still resolves to QA-2048.
5. Inspect the independent record oracle and verify the reference string and key are byte-for-byte unchanged while only the intended title changed.

## Expected results

- The mixed-direction reference remains associated with the correct ticket on screen.
- Navigation reaches the documented adjacent record despite mirrored layout.
- Persistent key and reference strings retain their exact original ordering and punctuation.

## False-pass traps

- Recognizing the digits 2048 somewhere on screen does not prove the complete identifier is displayed correctly.
- A mirrored arrow icon can hide an unchanged and now misleading navigation action.

## Cleanup

- Restore the original fixture title and locale preference.

## 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 first test](/docs/agent-qa/guides/first-test.md)
- [agent-qa hooks](/docs/agent-qa/guides/hooks.md)
- [agent-qa test](/docs/agent-qa/configuration/test.md)

- [Localization QA recipes](/agent-library/localization.md)
- [Software factory QA library](/agent-library.md)