Changelog
What's new in Regresco
May 2026
Business plan
- ·New Business tier ($149/month): 1000 runs, 100 projects, priority queue. Useful when 200 runs starts to feel tight or when test runs from one team should jump ahead of cron schedules from another
- ·Free tier and Pro tier unchanged. Same features on every plan, only the limits differ
April 2026
AI, Reliability & Billing
- ·Jira integration: auto-file a Jira issue for every failed step in a run. Per-project config (URL, email, API token, project key, issue type) with encrypted token storage. Description uses Atlassian Document Format for proper rendering
- ·Auto-heal: when a selector breaks at runtime we retry with an alternative and, if it passes, mark the step as auto-healed. Edit Flow shows the healed value with one-click Apply
- ·Sign in with Google or GitHub: one-click login, no password needed
- ·Self-serve Pro upgrade with subscription management ($49/month)
- ·Simplified pricing: Free and Pro plans, all features included on both
- ·Natural language flows: describe what to test in plain text, AI creates the flow
- ·Failure explanation: understand why a test failed with one click
- ·Smart locator healing: suggests better selectors when elements break
- ·Flaky test detection: automatically flags unstable steps across run history
- ·Single flow runs: re-run individual flows without running the whole project
- ·Email notifications: get notified when runs complete or fail
- ·Parallel flow execution: up to 3 flows run concurrently, faster results
- ·Adaptive timeouts and auto-retry on transient failures
- ·Flow stability trends: see pass/fail history per flow at a glance
- ·Real-time dashboard: runs update live without page refresh
- ·Browser console capture: see JS errors and warnings alongside test results
- ·Actionable error messages: every failure includes a specific fix suggestion
March 2026
Launch
- ·Cloud test execution with Playwright
- ·Test generation: crawls your site and suggests flows with real selectors
- ·Import existing Playwright tests (.spec.ts files)
- ·API steps: setup, auth, cleanup, and assertions within flows
- ·Automatic failure classification: regression, broken locator, flaky
- ·Baseline comparison: see what changed between runs
- ·Screenshots and Playwright traces for every run
- ·Scheduled runs: daily or weekly with time picker
- ·CI/CD webhook: trigger runs from your deploy pipeline
- ·Analytics dashboard: pass rate, failure breakdown, daily trends