Continuous Test Intelligence for Engineering Teams.
One command connects OyaCloud to your existing CI pipeline — no migration, no new framework required.
From there, every test run is linked across builds, branches, and environments, so you can instantly compare history, spot flaky tests, track regression trends, and answer quality questions with confidence — no more digging through one build at a time.
30-day free trial · No infrastructure to manage
See a Test Run Become Test Intelligence
Follow one CI run as OyaCloud turns isolated test results into branch health, regression trends, and root-cause analysis. Click any step to explore.
Or click any step on the left to jump straight there
Everything Your CI Doesn't Tell You
Historical context, branch comparisons, environment health, flaky test detection, regression insights, and automation stability — all in one place.
Upload from anywhere in one command
Your results files stay where they are. Point the CLI at your output directory — OyaCloud handles classification, deduplication, and storage automatically.
- ✓Works from CI runners, local machines, or scheduled jobs
- ✓Playwright, Cypress, JUnit, TestNG, and pytest all supported
- ✓Build ID returned immediately — results appear in your dashboard in seconds
| # | Test | Suite | Flip Rate | Last 10 Runs | Avg Dur. | First Seen |
|---|---|---|---|---|---|---|
| 1 | oauth_redirect_test | Auth | 34% | 1.4s | 3w ago | |
| 2 | cart_total_update_check | Cart | 21% | 0.8s | 1w ago | |
| 3 | email_delivery_under_3s | Notify | 14% | 2.1s | 5d ago |
One dashboard for every signal that matters
Stop checking multiple tools. Failing suites, declining pass rates, blocked PRs, and flaky tests — surfaced in one live view across all your projects.
- ✓All projects in a single pane with health indicators
- ✓Live-updating data with no manual refresh
- ✓Activity feed with full build context on every row
Know if a PR introduced new failures before review
Every PR run gets an automatic verdict against the last baseline on the same branch, environment, and suite. Your team knows immediately — before code review starts.
- ✓Exact new-failure count, not just "tests failed"
- ✓New failures vs known flaky clearly distinguished
- ✓Links directly into error details and AI root cause
| Build | Project | Branch | Test Summary | Status | Context Insight | Time |
|---|---|---|---|---|---|---|
b9d12e⇌ Post-Merge fix: cart quantity update | Mobile App | main | 0/50 | ⊗ Failed | 4 new failures | 12m ago |
a3f91c⇌ Post-Merge feat: OAuth login flow | Web App | main | 0/50 | ⊙ Passed | Clean | 1h ago |
c7e44a⇌ Post-Merge refactor: checkout flow | Web App | main | 0/50 | ⊙ Passed | 2 known flaky | 3h ago |
Track what every merge introduced to main
Post-merge runs capture how your main branch test suite changes after each commit. Catch regressions before they compound across the next sprint.
- ✓Pass-rate history per suite and environment
- ✓Surface regressions before the next release
- ✓Compare staging vs production in the same view
Schedule full test runs and see what slipped
Run nightly or weekly regressions independently from PR and post-merge builds. Get a clear picture of what is consistently failing versus newly broken.
- ✓Separate tab — never mixed with PR or post-merge data
- ✓Trend over days and weeks in the same view
- ✓Drill into any run for the full test-by-test breakdown
| Build | Project | Environment | Test Summary | Status | Context Insight | Time |
|---|---|---|---|---|---|---|
c7e44a▷ Regression | Web App | staging | 0/50 | ⊙ Passed | 2 known flaky | 2h ago |
d2c09f▷ Regression | Web App | prod | 0/50 | ⊗ Failed | 3 failures | 6h ago |
e5a11b▷ Regression | Mobile App | staging | 0/50 | ⊙ Passed | Clean | 8h ago |
2 tests in the Auth suite are failing due to a timing issue in the OAuth redirect flow. The dashboard header element is not visible within the expected timeout — likely a race condition introduced in this PR.
Add an explicit wait for the redirect to complete before asserting on dashboard state. Consider page.waitForURL or increase the default timeout for this suite.
Root cause analysis, not just stack traces
OyaCloud analyzes failure patterns and error messages to explain what actually went wrong — and where to look first. You get a suggested fix, not just a log.
- ✓Pattern analysis across multiple failures in one run
- ✓Suggested fix in plain language, not raw stack output
- ✓Powered by AWS Bedrock, running on your data
Health visibility across every environment
Staging, production, dev — each environment gets its own pass-rate trend, build health strips, and flaky test list. No more environment-specific blind spots.
- ✓Per-environment flaky and failing test breakdown
- ✓PR, Post-Merge, and Regression tracked separately per env
- ✓Click into any environment for full trend drill-down
Three commands to your first insight
No infrastructure to provision. No agent to deploy. Works with your existing CI.
Install the CLI
One global install. Works on any machine or CI runner.
npm install -g oyacloudSet your API key
Get your key from the dashboard after signing up — free, no card required.
oyacloud config set-key YOUR_KEYOne command, done
From CI, a scheduled regression run, or your local machine — point at your results directory.
oyacloud upload \
--framework playwright_ts \
--results-dir test-resultsYour dashboard populates on first upload — pass rates, PR comparisons, and flaky tests, immediately.
Bring your existing tests — no migration required
Point the CLI at your existing output directory. No code changes needed.
Turn your test runs into answers.
30-day free trial. One command to ship. No infrastructure to manage.
Start free trialAlso from OyaPlus — a different kind of service
Need automation built from scratch? We deliver it.
OyaPlus builds production-ready automation for web, mobile, or API — in whatever stack you already use. Live in 2 weeks, fully integrated with OyaCloud.
Learn about QA services →