All features
Everything Squally does.
For every Playwright run in CI.
33 features in five groups. Each one says where you find it in the app.
Insights
How stable your suite is, and where it costs you time.
Overview
Stability, flaky tests, failing tests and time lost for a branch and a period, each compared with the period before.
Overview
Where the time goes
The tests whose failures and retries cost the most CI time.
Overview
Failing and flaky tests
The tests that failed or needed a retry most often, with their rates.
Overview
Branch health
Passed, flaky and failed runs and the median duration of every branch.
Overview
Runs
Every run grouped by day, with its result bar, branch, commit and author.
Runs
Test explorer
Stability, flaky rate, failure rate and time lost per test, with its last ten results.
Test explorer
Test history
Runs per day, median duration and every run of one test.
Test page
Run comparison
Newly failing, fixed, still failing and slower tests between two runs.
Run page
CI and local runs
Runs from your machine are kept apart from CI and have their own numbers.
Everywhere
Debugging
Everything a failed test left behind, in one place.
Error explorer
One error across all runs and tests, with first and last seen.
Error explorer
What went wrong
The errors of a run, marked new or seen before, with the code frame.
Run page
Every attempt
Each retry as its own tab, with its error, stack trace and duration.
Attempt page
Screenshots
The page at the moment the test failed.
Attempt page
Playwright traces
Open the trace in the Playwright trace viewer in one click.
Attempt page
Browser console and test output
What the page and the test printed, per attempt.
Attempt page
Shards and re-runs
Shards report as one run. A re-run of failed jobs links to the run it repeats.
Run page
Search
Jump to any run, test, error or page with ⌘K.
Everywhere
AI
Help with a failed test, in Squally or in your own agent.
Fix with Squally
A likely cause and numbered steps for one failed attempt, based on its error, stack and page state.
Attempt page
Fix in your agent
A ready prompt for Claude Code, Cursor or Codex, or the full failure context to copy.
Attempt page
MCP server
Your coding agent reads runs, tests and errors through squally-mcp.
Your editor
Read API
The same data over a REST API, with read keys for your organization.
API
Workflow
Results where your team already looks.
GitHub checks
A check on every commit, one per CI job.
GitHub
Pull request comment
One comment per pull request, updated with every run.
GitHub
Slack
A summary of every run in your channel.
Slack
Weekly reports
One email a week with what needs attention, for the branch you pick.
Email
Run reports
Print a run or copy it as Markdown for a ticket.
Run page
CI providers
GitHub Actions, GitLab, Jenkins, Buildkite and more; a link back to the CI run where the provider has one.
Reporter
Setup and data
One line to start, and clear rules for your data.
One reporter line
Add squally-reporter to playwright.config.ts. Results arrive while the suite runs.
Playwright
Matrix jobs
Job keys keep browser and suite matrices apart.
Reporter
Stored in the EU
Runs, results and artifacts are stored in Frankfurt.
Hosting
No access to your code
The GitHub app reads checks and pull requests, never your repository contents.
GitHub
Members and projects
Admins and members per organization, several projects per organization.
Settings
Data retention
Runs and artifacts are deleted on a fixed schedule.
Settings
Missing something you need?
Write to support@squally.dev. The beta shapes what comes next.