Introduction
Overview
What is Automation Export?
Transform your manual test cases into executable automation projects across multiple frameworks.
The Automation Export feature converts your SynthQA test suites into complete, production-ready test projects for your preferred framework. Export once, run anywhere — locally or in your CI/CD pipeline.
- One-click export of entire test suites
- Six supported frameworks: Playwright, Cypress, Selenium, Puppeteer, TestCafe, WebDriverIO
- Complete project structure with all dependencies
- Pre-configured settings and test files
- Test data snapshots for reference and validation
- Ready for CI/CD integration (GitHub Actions, GitLab CI, etc.)
Instant automation
Export transforms your test cases into a working project in seconds — complete with project structure, dependencies, configuration, and test specs ready to run.
| Feature | Manual Testing | Automation Export |
|---|---|---|
| Execution time | Minutes to hours per test | Seconds per test |
| Repeatability | Varies by tester | 100% consistent |
| Regression testing | Time-intensive | Run anytime, instantly |
| CI/CD integration | Not applicable | ✓ Full support |
| Initial setup | None | ~5 minutes (one-time) |
Prerequisites
What you need before exporting tests.
- Active SynthQA account (Pro plan)
- At least one test suite with test cases
- Node.js 18+ installed on your machine (for running tests)
- Basic understanding of command line operations
- Optional: Test cases with defined test steps for richer automation
Choose your stack
Supported Frameworks
All supported frameworks
SynthQA exports to all major web automation frameworks.
| Framework | Language | Best For | SynthQA Support |
|---|---|---|---|
| Playwright | TypeScript / JS | Modern web apps, cross-browser | Full export |
| Cypress | JavaScript | Frontend-heavy apps, E2E | Full export |
| Selenium | Java / Python / JS | Legacy apps, enterprise | Full export |
| Puppeteer | JavaScript | Chrome automation, scraping | Full export |
| TestCafe | JavaScript | No-driver cross-browser testing | Full export |
| WebDriverIO | JavaScript | Web + mobile, W3C WebDriver | Full export |
Quick start
Getting Started
Three simple steps
From test suite to running automation in minutes.
1
Navigate
Go to your test suite and click the "Automation" button to access the Automation Hub.
2
Choose & Export
Select your framework, then click "Export" to download a complete project as a ZIP file.
3
Run
Extract the ZIP, install dependencies, configure your environment, and run your tests.
Typical timeline
First-time setup: 5–10 minutes. Subsequent exports: 2–3 minutes from export to running tests.
Step-by-step
Automation Hub
Download
Exporting Tests
Export process
How to export your suite as an automation project.
What happens when you export:
- Select your framework in the Automation Hub
- Click "Export to [Framework]"
- System generates a complete project (5–10 seconds)
- ZIP file downloads automatically
- File name:
synthqa-[framework]-[suite-name].zip
Download confirmation
A success notification confirms the export. Check your browser's downloads folder for the ZIP file.
Understanding the export
Project Structure
Configuration
Setup & Installation
Execution
Running Tests
Run commands by framework
Each framework has its own run command — all are pre-configured in the exported
package.json.pnpm test # headless pnpm test:headed # with browser UI pnpm test:debug # Playwright Inspector
Advanced
Enhancement Options
Automation metadata
Pre-fill your tests with selectors, URLs, and test data across any framework.
Instead of exporting tests with TODO placeholders, you can enhance test cases with automation metadata to generate pre-filled, near-ready tests regardless of which framework you use.
❌ Without metadata
// TODO: Navigate to login page
await page.goto('???');
// TODO: Fill email field
await page.fill('???', '???');✅ With metadata
// Navigate to login page
await page.goto('/login');
// Fill email field
await page.fill('#email',
'test@example.com');80% time savings
With automation metadata, tests are 90% ready to run. You only need to verify and fine-tune instead of implementing from scratch.
Quality
Best Practices
Selector strategies
Choosing reliable selectors — applies to all frameworks.
✅ Best: Test IDs
[data-testid="login-btn"]
Stable, explicit, purpose-built for testing
⚠️ OK: IDs / Names
#email-input
Reasonable if they're stable and semantic
❌ Avoid: CSS Classes
.btn-primary
Fragile — changes with styling updates
Do's and Don'ts
✅ Do
- Define test steps before exporting
- Use descriptive suite and test names
- Keep tests independent and isolated
- Use environment variables for test data
- Re-export when test cases are updated
- Commit your exported project to version control
❌ Avoid
- Tests that depend on each other
- Hardcoded URLs and credentials in tests
- Exporting suites with no test steps defined
- Ignoring failed tests without investigation
- Committing .env files to version control
- Mixing multiple features in one suite
Common issues
Troubleshooting
FAQ
Frequently Asked Questions
Help
Support
Getting help
Contact options:
- Email: support@synthqa.app
- Use the feedback button in your dashboard
When reporting export issues, include:
- Suite ID and name
- Framework selected
- Browser console errors (if any)
- Whether download started or failed silently
Additional resources:
Last updated: March 2026 · Guide version: 2.0