December 5, 2025
Paragon E2E: Natural Language End-to-End Testing
Shane Barakat, Polarity Labs, Research Division
Paragon now supports end-to-end testing through natural language. Describe what you want to test in plain English, and Paragon writes, runs, and iterates on Playwright tests.
Feature Launch Video
The Problem with E2E Testing
End-to-end testing catches the bugs that unit tests miss: integration failures, UI regressions, and the cross-system issues that slip into production. But writing E2E tests is tedious. Playwright and Cypress are powerful frameworks, but authoring tests means learning APIs, writing selectors, handling async behavior, and debugging failures through trial and error.
Most teams know they should have better E2E coverage. Few have the time to write and maintain the tests.
How Paragon E2E Works
Instead of writing Playwright code yourself, you describe what you want to test directly in CLI input:
"Test the checkout flow with an expired credit card""Verify the dashboard loads correctly for users with no data""Thoroughly test that file upload handles large images gracefully"Paragon interprets your description, generates the appropriate Playwright tests, and executes them against your local environment. When complete, it opens the Playwright HTML report so you can review results with tracing and video recordings.
The tests run on your actual machine with your real environment variables, local services, secrets, and configurations. This ensures simple setups and no artificial test environments that differ from reality.
How It Works
Saved Automation Scenarios
Paragon also supports saved automation scenarios for repeatable test runs. You can trigger these through multiple interfaces:
Through chat by asking "run my e2e tests" or "run the checkout-flow scenario," or through the TUI with `ctrl+p` to open the automation picker.
These saved scenarios execute pre-defined shell command sequences, which is separate from the natural language test generation described above.
CLI Integration
Run tests directly from your terminal with simple commands.
Iterative Refinement
Paragon automatically retries and fixes failing tests.
Local Environment
Tests run with your real services, secrets, and configs.
Persistent Files
Generated tests stay in your repo for inspection and modification.
Why This Matters
E2E testing becomes accessible when the barrier is a sentence instead of a script. Teams that previously skipped end-to-end coverage due to time constraints can now validate critical flows in the time it takes to describe them.
Traditional E2E vs Paragon
You still get all the benefits of Playwright: browser automation, detailed reporting, and whatever additional configuration you want to add. Paragon handles the authoring so you can focus on what to test rather than how to test it.
Available now in Paragon at home.polarity.cc.