Import Your Existing Test Framework: Web, iOS, and Android
Bring Cypress, Selenium, Playwright, Appium, Detox, Maestro, and more into Validate.QA. Full from→to map: what each platform imports, what we output, GitHub/upload sources, and incremental re-import.
Most teams do not start QA from zero. They already have Cypress specs in a monorepo, a Selenium grid nobody wants to babysit, Detox flows that only run on one engineer’s laptop, or a Maestro folder that never made it into CI. The tests encode real product knowledge — login paths, checkout edge cases, permission gates — but they live in a framework the team is trying to leave, or in a stack that does not share a dashboard with the web suite.
Validate.QA’s Framework Import is a second ingestion mode alongside recording, voice-guided capture, and autonomous discovery. Point it at an existing test repository — a GitHub repo or a .zip / .tar.gz archive — and an AI auditor reads the suite, extracts every test case, translates it into Validate.QA’s native format, and lands the results in your project as Features and runnable tests. Web imports become Playwright. Mobile imports become Appium. Same health dashboard, same healing loop, same CI hooks.
This post is the full map: what you can import from, what Validate.QA produces to, how web and mobile differ, and what to expect on the first run.
Two Platforms, One Import Wizard
When you open Import tests in the dashboard, the first decision is permanent for the project: Web or Mobile (iOS / Android). That lock is intentional — web tests run against a configured BASE_URL with Playwright; mobile tests launch a bundle ID or package name on a simulator, emulator, or USB device via Appium. Mixing both in one project would confuse runners, variables, and healing context, so you pick the surface area once and import into it.
On both Web and Mobile, you also choose between two methods:
Recording and AI Mobile Discovery remain separate entry points on the same platform.
Web: What We Import From → What You Get
The web importer detects your stack from repo layout, config files, and test syntax, then translates each test into a standalone @playwright/test spec. If the source is already Playwright, we adapt minimally. If it is another framework, we preserve intent, steps, and assertions as faithfully as Playwright allows.
Topics: Framework Import, Migration, Playwright, Appium, iOS, Android.
Read the full article · Get Started Free