# e2e > An open framework for agentic end-to-end testing. - [Introduction](https://e2e.com/docs/index.md): Open source AI testing for web and mobile apps. Spend less time on tests and more time building. - [Quickstart](https://e2e.com/docs/quickstart.md): Set up e2e with one prompt to your coding agent, or step by step. - [Core concepts](https://e2e.com/docs/core-concepts.md): Goals, assertions, and locators, and how to structure and run tests with them. - [Agentic or deterministic](https://e2e.com/docs/agentic-vs-deterministic.md): Choose agentic or deterministic actions and assertions for your end-to-end tests. - [Coding agents](https://e2e.com/docs/coding-agents.md): Give a coding agent the skill, a live app session, and reports it can use to write and debug tests. - [MCP server](https://e2e.com/docs/mcp-server.md): Let your coding agent use your app and check its own work. - [Setting up CI](https://e2e.com/docs/ci.md): Run e2e on GitHub Actions, Vercel deployments, GitLab CI/CD, Expo Workflows, Bitrise, Codemagic, Norrix, or any CI service that runs Node. - [Web](https://e2e.com/docs/web.md): Point the web engine at your app or let the runner start it, and run a suite at several viewport sizes. - [Mobile](https://e2e.com/docs/mobile.md): Set up a simulator, emulator, or connected phone as a target, write a device test, and know what differs from the web. - [API](https://e2e.com/docs/api-testing.md): Check your API with fetch and value matchers, in the same files and run as UI tests. - [@e2e-dev/core](https://e2e.com/docs/core.md): Drive a browser or a native app from plain code, with an optional agent and no test runner. - [Caching](https://e2e.com/docs/cache.md): Replay verified agent actions without model calls, and let the agent take over when the app changes. - [Exploring without a test](https://e2e.com/docs/explore.md): Give the agent a goal, not a test file. It plans its steps, operates the app, and reports what it finds. - [Visual comparison](https://e2e.com/docs/visual-testing.md): Compare the screen, or one element, against a stored screenshot on the web, iOS, and Android with the same test. - [Authentication](https://e2e.com/docs/authentication.md): Sign in once, reuse the session across tests, and pass secrets without exposing them to the model. - [Bug bashes](https://e2e.com/docs/bug-bash.md): Run many explore sessions at the same time, then prove each bug with a failing test. - [Agents and personas](https://e2e.com/docs/agents.md): Configure several agents in one suite, pin tests to them, and run one flow as each persona. - [Models](https://e2e.com/docs/models.md): Configure a model with your own subscription, an API key, or a local server. - [Decision models](https://e2e.com/docs/decision-models.md): Run bounded actions with a decision model and a small text model instead of a full LLM agent. - [Subscriptions](https://e2e.com/docs/subscriptions.md): Use your ChatGPT, GitHub Copilot, OpenCode Console, or SuperGrok subscription, your Claude Max or Team plan's API credits, or your Claude Code or Codex login for agent steps. - [GitHub Actions](https://e2e.com/docs/ci/github-actions.md): Run web, iOS, and Android tests on GitHub Actions, upload the reports, and post the results on the pull request. - [Vercel Previews](https://e2e.com/docs/ci/vercel-previews.md): Test Vercel preview and production deployments with GitHub Actions, and hold production releases until e2e passes. - [GitLab CI/CD](https://e2e.com/docs/ci/gitlab.md): Run web, iOS, and Android tests on GitLab CI/CD, show the results in the merge request, and run only the tests a merge request can affect. - [Expo Workflows](https://e2e.com/docs/ci/eas-workflows.md): Build an Expo app with Expo Build and run iOS and Android tests on it in an Expo workflow. - [Bitrise](https://e2e.com/docs/ci/bitrise.md): Run iOS and Android tests on Bitrise with one workflow for each platform in a pipeline. - [Codemagic](https://e2e.com/docs/ci/codemagic.md): Run iOS and Android tests on Codemagic, on a Mac mini for iOS and a Linux instance for Android. - [Norrix](https://e2e.com/docs/ci/norrix.md): Build a NativeScript app with Norrix and run its e2e suite on a Norrix simulator or emulator. - [GitHub PR comments](https://e2e.com/docs/github.md): The @e2e-dev/github reporter posts one comment per run from GitHub Actions and keeps it current. - [Overview](https://e2e.com/docs/integrations/index.md): Official integrations with hosted browser and device services, one package per service. - [Kernel](https://e2e.com/docs/integrations/kernel.md): Run web targets in Kernel's hosted Chromium with the kernel() browser provider from @e2e-dev/kernel. - [Browser Run](https://e2e.com/docs/integrations/browser-run.md): Run web targets in Cloudflare's hosted Chromium with the browserRun() browser provider. - [Notte](https://e2e.com/docs/integrations/notte.md): Run web targets in Notte's cloud browsers with the notte() browser provider from @e2e-dev/notte. - [Lightpanda](https://e2e.com/docs/integrations/lightpanda.md): Run web targets in Lightpanda, the open-source headless browser, with the lightpanda() browser provider from @e2e-dev/lightpanda. - [Moli](https://e2e.com/docs/integrations/moli.md): Run web targets in local Moli browsers with automatic startup and cleanup through @e2e-dev/moli. - [Expo Simulators](https://e2e.com/docs/integrations/eas.md): Run mobile targets on Expo Simulators' hosted iOS simulators and Android emulators with the expoSimulators() device provider from @e2e-dev/eas. - [smol machines](https://e2e.com/docs/integrations/smol.md): Run each web test attempt in its own branch of a warm Chromium microVM on your computer with the smol() browser provider from @e2e-dev/smol. - [Limrun](https://e2e.com/docs/integrations/limrun.md): Run mobile app tests on hosted iOS simulators and Android emulators. - [TestMu AI](https://e2e.com/docs/integrations/testmu.md): Run mobile targets on TestMu AI (formerly LambdaTest) emulators, simulators, and real devices, and web targets in its hosted Chrome and Edge, with @e2e-dev/testmu. - [BrowserStack](https://e2e.com/docs/integrations/browserstack.md): Run mobile targets on BrowserStack App Automate real Android and iOS devices with the browserstack() device provider from @e2e-dev/browserstack. - [E2B](https://e2e.com/docs/integrations/e2b.md): Run Android targets and web targets in E2B sandboxes with the e2b() and e2bBrowsers() providers from @e2e-dev/e2b. - [Revyl](https://e2e.com/docs/integrations/revyl.md): Run mobile app tests on Revyl's hosted iOS simulators and Android emulators with @e2e-dev/revyl. - [Community packages](https://e2e.com/docs/community-packages.md): Find third-party packages that extend e2e and submit an integration. - [Project tools](https://e2e.com/docs/tools.md): Add tools for test APIs, data setup, and device operations. - [Writing fixtures](https://e2e.com/docs/fixtures.md): Create test data and other resources before each test and clean them up after it. - [Custom executors](https://e2e.com/docs/executors.md): Customize the agent loop or implement your own step executor. - [Test filters](https://e2e.com/docs/filters.md): Run only the tests a pull request can affect. - [Engines](https://e2e.com/docs/engines.md): Choose how to build an engine for a UI platform, in TypeScript or any other language. - [Writing an engine](https://e2e.com/docs/writing-an-engine.md): Implement the e2e engine contract for another UI platform. - [Engine servers](https://e2e.com/docs/engine-servers.md): Run an engine in another process, on another machine, or in another language. - [Working with the browser](https://e2e.com/docs/browser.md): Mock an API, handle a dialog, download a file, reach into an iframe, and pick a browser. - [Security](https://e2e.com/docs/security.md): What the model can see and do, how secrets stay out of it, and what you still need to watch. - [Telemetry](https://e2e.com/docs/telemetry.md): What the CLI sends, what it never sends, and how to turn it off. - [Debugging a run](https://e2e.com/docs/debugging.md): Read the trace page, open the evidence, watch the browser, and see what the model was sent. - [How agent steps work](https://e2e.com/docs/agent-steps.md): What the model sees, what it may do, how a step ends, and what it costs. - [Self-healing tests](https://e2e.com/docs/self-healing.md): How a replayed agent step recovers when the UI changed, and how the recording repairs itself. - [Page objects](https://e2e.com/docs/page-object-model.md): Wrap one screen's locators and actions in a class, and hand it to tests as a fixture. - [Overview](https://e2e.com/docs/migrate/index.md): Move a Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one test at a time. - [From Playwright](https://e2e.com/docs/migrate/playwright.md): Run e2e alongside Playwright and migrate tests one file at a time. - [From Cypress](https://e2e.com/docs/migrate/cypress.md): Replace Cypress command chains with async tests and keep your data-cy attributes. - [From Selenium](https://e2e.com/docs/migrate/selenium.md): Rewrite Selenium flows in TypeScript with locators, retrying assertions, and agent goals. - [From Appium](https://e2e.com/docs/migrate/appium.md): Move Appium and WebdriverIO mobile tests to TypeScript with locators, device calls, and agent goals. - [From Detox](https://e2e.com/docs/migrate/detox.md): Use your existing app build and testIDs with screen, expect, and agent goals. - [From Maestro](https://e2e.com/docs/migrate/maestro.md): Move Maestro flows to TypeScript with locators, assertions, and agent goals. - [From TesterArmy](https://e2e.com/docs/migrate/testerarmy.md): Turn TesterArmy saved tests into e2e tests that run in your repository and CI. - [test](https://e2e.com/docs/reference/test.md): Tests, setup tests, groups, hooks, options, and fixtures. - [expect](https://e2e.com/docs/reference/expect.md): Locator assertions, fixture assertions, and plain value matchers. - [screen and Locator](https://e2e.com/docs/reference/screen.md): Queries, refinement, actions, and reads. - [app](https://e2e.com/docs/reference/app.md): The portable app lifecycle fixture, available on every platform. - [agent](https://e2e.com/docs/reference/agent.md): Run agent actions, check conditions, and extract structured data. - [@e2e-dev/core](https://e2e.com/docs/reference/core.md): launch, hosts, sessions, saved state, and createAgent, the API of a program that drives a browser or a device without the test runner. - [E2EConfig](https://e2e.com/docs/reference/config.md): Every configuration key, its default, its valid range, and the environment variables. - [CLI](https://e2e.com/docs/reference/cli.md): Commands, flags, output formats, and exit codes. - [e2e/runner](https://e2e.com/docs/reference/runner.md): Run a test suite or an exploration, list a selection, or host e2e sessions in another test runner. - [MCP server (e2e mcp)](https://e2e.com/docs/reference/mcp.md): Let a coding agent inspect and interact with your app over MCP. - [Reporters](https://e2e.com/docs/reference/reporters.md): Receive run events and publish results with a custom reporter. - [Environment variables](https://e2e.com/docs/reference/environment.md): Every variable the runner and the first-party engines read, and what each one does. - [Errors](https://e2e.com/docs/reference/errors.md): Every code you can see, its class, and its exit code. - [Security rules](https://e2e.com/docs/reference/security.md): Every rule the runner enforces on model input, tool calls, secrets, redaction, sessions, the replay cache, artifacts, and network connections. - [Browser](https://e2e.com/docs/reference/web.md): The browser engine, its options, and the browser fixture it contributes. - [Mobile](https://e2e.com/docs/reference/mobile.md): Mobile engine options and the device fixture for iOS and Android. - [e2e/engine](https://e2e.com/docs/reference/engine.md): Build an engine with observations, actions, lifecycle hooks, and fixtures. - [Engine protocol](https://e2e.com/docs/reference/engine-protocol.md): Run an engine in another process, on another machine, or in another language.