> For the complete documentation index, see [llms.txt](https://learning.contextqa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learning.contextqa.com/migrate-to-contextqa.md). # Migrate to ContextQA - [Migration Overview](https://learning.contextqa.com/migrate-to-contextqa/migration.md): Choose a safe ContextQA migration path for Playwright, Selenium, Tricentis Tosca, or mabl while preserving assertions, data, evidence, and rollback. - [Planning & Acceptance Checklist](https://learning.contextqa.com/migrate-to-contextqa/planning-checklist.md): Inventory source tests, preserve assertions and dependencies, compare parallel runs, control cutover, and document rollback for a ContextQA migration. - [Migrate from Playwright](https://learning.contextqa.com/migrate-to-contextqa/playwright-to-contextqa.md): Analyze a Playwright repository, map fixtures and projects, migrate a representative slice, verify assertions and failures, and cut over safely to ContextQA. - [Migrate from Selenium](https://learning.contextqa.com/migrate-to-contextqa/selenium-to-contextqa.md): Inventory Selenium runners, page objects, waits, grids, data, and assertions; migrate a representative slice to ContextQA and verify behavior safely. - [Migrate from Tricentis Tosca](https://learning.contextqa.com/migrate-to-contextqa/tricentis-tosca-to-contextqa.md): Inventory Tosca requirements, TestCases, Modules, TestCase-Design, data, and ExecutionLists; rebuild a verified pilot in ContextQA without claiming a direct importer. - [Migrate from mabl](https://learning.contextqa.com/migrate-to-contextqa/mabl-to-contextqa.md): Export representative mabl browser tests, reconcile unsupported steps and artifacts, migrate the reviewed code or intent to ContextQA, and verify parity. - [MCP-Assisted Existing-Suite Migration](https://learning.contextqa.com/migrate-to-contextqa/migrating-existing-tests.md): Analyze a Selenium, Cypress, or Playwright repository, preview an MCP-assisted ContextQA migration, migrate the tests, and verify the results. --- # 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://learning.contextqa.com/migrate-to-contextqa.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.