WrightTest WrightTest

Roadmap

Roadmap

WrightTest is focused on making Playwright-based browser checks easier to create, run, schedule, and debug from a self-hosted web interface. This roadmap describes planned and considered improvements. It is not a guarantee of delivery dates or final scope.

Current focus

  • Self-hosted browser check automation.
  • Visual check editing.
  • Scheduled execution.
  • Run result debugging with screenshots and traces.
  • Environments and reusable variables.
  • Telegram and Slack alerts.
  • Docker-first deployment.

Planned

Better check authoring

  • More step types and assertion types.
  • Better validation for incomplete steps.
  • Improved locator editing and copying.
  • Better import from existing Playwright .spec.ts files.
  • Better export options for stable checks.

Run diagnostics

  • Better failed-step highlighting.
  • Dedicated failed screenshot preview.
  • Easier navigation between step results, screenshots, and traces.
  • Better display for long locators and raw errors.
  • More useful failure summaries.

Schedules and automation

  • Better schedule history.
  • More readable cron presets.
  • Pause and resume improvements.
  • Schedule-level failure summaries.
  • Better handling for overdue schedules.

Alerts

  • Better alert delivery status.
  • More notification providers.
  • Better recovered-state handling.
  • Test notification history.
  • Alert templates.

Documentation

  • More user guides.
  • More screenshots.
  • Recorder troubleshooting guide.
  • Schedules guide.
  • Alerts guide.
  • Runs and traces guide.

Under consideration

  • Firefox support.
  • WebKit support.
  • Role-based access control.
  • Team and workspace permissions.
  • More advanced secret handling.
  • Retention settings for screenshots and traces.
  • CI templates for GitHub Actions and GitLab CI.
  • API tokens for external integrations.
  • More detailed audit logs.
  • More advanced suite management.
  • Better mobile and device presets.

Not planned for the near term

  • Public multi-tenant SaaS hosting.
  • Replacing full Playwright codebases for complex engineering teams.
  • Full visual regression testing.
  • Real device farm testing.
  • Load testing.
  • API testing as a primary product area.

WrightTest may integrate with these workflows later, but the current focus is browser UI checks.

Known current limitations

  • Browser execution currently uses Chromium.
  • Firefox and WebKit are not supported in the current version.
  • Some complex interactions may need manual step adjustments.
  • WrightTest is intended for trusted internal or self-hosted usage.
  • Screenshots and traces may contain sensitive data.

Suggest a feature

Feature requests can be submitted through GitHub Issues.

  • The problem you are trying to solve.
  • The workflow where it appears.
  • Whether it affects check creation, running, scheduling, debugging, alerts, or deployment.
  • Screenshots or examples if useful.

GitHub Issues: https://github.com/AlexFilippov-it/wrighttest/issues