> For the complete documentation index, see [llms.txt](https://docs.mozark.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mozark.ai/test-infrastructure-documentation/test-infrastructure.md).
# Test Infrastructure
Start here to navigate the Testing Portal docs by workflow, platform topic, and support need.
## Test Infrastructure
Use this space to understand the Testing Portal and navigate to the relevant workflow or platform topic.
### Start here
* [Getting Started](/test-infrastructure-documentation/getting-started/create-your-first-workflow.md) — Access the portal, sign in, and select the appropriate organization, app, and project.
* [Product Overview](/test-infrastructure-documentation/getting-started/overview.md) — Understand the portal's main modules, services, and navigation model.
### Explore by workflow
* [Interactive Testing](/test-infrastructure-documentation/interactive-testing/overview.md) — Launch live manual test sessions across web, mobile, and TV platforms.
* [Automation](/test-infrastructure-documentation/automation/overview.md) — Connect Playwright and Appium suites to remote execution infrastructure.
* [Sessions](/test-infrastructure-documentation/sessions/overview.md) — Search, filter, and review interactive and automation session history.
### Shared platform topics
* [File Management](/test-infrastructure-documentation/file-management/overview.md) — Upload, organize, and reuse app builds and test assets.
* [UI and Navigation Behavior](/test-infrastructure-documentation/ui-and-navigation-behavior.md) — Understand themes, notifications, navigation, and shared interface patterns.
* [Permissions and Security](/test-infrastructure-documentation/permissions-and-security.md) — Review authentication, access control, and project-level isolation.
### Operational guidance
* [Known Limitations and Edge Cases](/test-infrastructure-documentation/known-limitations-and-edge-cases.md) — Review current constraints and release-specific behavior.
* [Best Practices](/test-infrastructure-documentation/best-practices.md) — Follow recommended patterns for sessions, bugs, files, and AI usage.
* [Troubleshooting & FAQs](/test-infrastructure-documentation/troubleshooting-and-faqs.md) — Resolve common issues with login, sessions, devices, files, and scheduled tests.
### Intended audience
* **QA engineers and manual testers** who run interactive sessions, file bugs, and review recordings.
* **Automation engineers** who connect Playwright or Appium suites, or use Optics AI workflows.
* **Engineering managers and stakeholders** who review coverage, session history, and quality outcomes.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.mozark.ai/test-infrastructure-documentation/test-infrastructure.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
