---
title: "Return to the intended route after fixture sign-in"
description: "Verify a protected deep link preserves its intended destination through the application login flow using an authorized test account and synthetic record."
canonical_url: "https://vostride.com/agent-library/navigation-routing/auth-return-destination.md"
md_url: "https://vostride.com/agent-library/navigation-routing/auth-return-destination.md"
content_kind: "recipe"
topic: "navigation-routing"
---

# Return to the intended route after fixture sign-in

Verify a protected deep link preserves its intended destination through the application login flow using an authorized test account and synthetic record.

## Risk

Authentication redirects can send every user to the dashboard and discard a deep link. This recipe tests application behavior with prepared credentials; it does not require bypassing MFA or capturing new auth state automatically.

## Fixtures

- A test-only account has an approved login method available in the isolated environment, with secrets supplied through supported secret handling.
- A protected record has key LOGIN-42 and a prepared deep link recorded in the seed manifest.
- The starting browser session is unauthenticated, and the product contract restores the original internal destination after successful login.

## Steps

1. Open the prepared protected record URL while signed out and verify the application presents its login flow.
2. Complete the approved test-account sign-in steps without printing credentials or token material.
3. Verify the resulting destination is the LOGIN-42 record, not only a generic signed-in landing page.
4. Verify its workspace label and distinctive fixture body agree with the seed manifest.
5. Reload the destination and verify the session remains valid for this journey and the same record detail renders.

## Expected results

- The unauthenticated route triggers the expected application sign-in boundary.
- Successful sign-in restores the original internal record identity under the specified return-path contract.
- The post-login record content and workspace context agree with the authorized fixture.

## False-pass traps

- A visible account menu proves authentication but not restoration of the intended destination.
- Manually reopening the deep link after landing on Dashboard would conceal a lost return-path defect.

## Cleanup

- Sign out the disposable browser session and delete the protected fixture record if no longer needed.

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