> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qa.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Cross-Application Tests

> Coordinate tests that span more than one application in the same project.

Many products are more than one app: a customer storefront and an admin console, or a web UI and an API. QA.tech models each as an [application](/core-concepts/applications-and-environments) with its own environments. Cross-application tests chain those apps with [dependencies](/core-concepts/dependencies).

## When you need this

* Create a resource in App A, verify it in App B
* Log in on the customer site, then assert something in an admin app
* Drive a browser test and an [API test](/core-concepts/api-testing) against the same feature

## Patterns

| Need | Mechanism |
| :- | :- |
| Share an ID or URL across apps or sessions | [Wait For](/core-concepts/dependencies#wait-for) plus [output values](/core-concepts/dependencies#data-sharing-between-tests) |
| Continue the same browser session | [Resume From](/core-concepts/dependencies#resume-from) — only when both tests use the **same Environment** |
| Multi-user collaboration | Separate login roots so each user has an isolated session; see [Multi-User Testing Scenarios](/core-concepts/dependencies#multi-user-testing-scenarios) |

Resume From does not work across different Environments, even when the URLs look similar. Wait For with output values is the usual choice when App A and App B each have their own environment.

## Related

* [Applications & Environments](/core-concepts/applications-and-environments)
* [Test Dependencies](/core-concepts/dependencies)
* [Configs](/core-concepts/configs) — credentials and data per application