Intent-driven tests as code
Describe a journey in plain English and blop turns it into a `.blop.ts` test that reads as intent rather than a selector script. The test lives in your repo and can be reviewed like other code.
blop
Freemium
Blop writes browser tests as code, runs them in CI, clusters repeated failures, and opens pull requests to fix broken tests.
What is blop?
Blop is a QA agent for teams that want browser tests to live as code in their repository instead of in a vendor dashboard. You describe a journey in plain English, and the agent runs a real browser through it to create and maintain a test artifact you own.
The product runs those tests in your CI, posts structured results back to the pull request that triggered them, and clusters repeated failures so recurring breakages are easier to track. When UI changes break a test, Blop can open a pull request with a fix and verification step, keeping the workflow centered on reviewable diffs.
What can blop do?
Browser runs backed by Playwright
The agent drives a real browser through the flow over Playwright, so the test outcome reflects an actual user path rather than a hidden dashboard state.
CI-native execution
Blop runs tests in your CI using your existing GitHub Actions runners, so the workflow fits into the pipeline you already operate.
Failure clustering
Repeated failures are grouped into clusters so the same broken selector or UI change does not appear as dozens of separate rows across runs.
Agent-authored repair PRs
When a failure is eligible, the agent can open a pull request that fixes the test and verifies it green before review. Auto-fix is described as early access.
Synthetic monitoring
Any test can also be scheduled as a recurring probe against production, with uptime, p95 duration, and journey completion shown as signals.
Use Cases
“Turn product journeys into code”
Teams can describe a checkout, signup, or other user journey in plain English and get a browser test that can be versioned and reviewed alongside product changes.
“Triage repeated failures”
When the same selector breakage or UI regression shows up repeatedly, failure clustering turns many similar results into one issue to investigate.
“Repair tests through pull requests”
If a UI change breaks a test, the agent can inspect the trace, console output, and diff, then open a pull request with a scoped repair and verification run.
“Fit into an existing CI workflow”
Teams that already use GitHub Actions can run tests through their current CI runners instead of hosting a separate execution environment.
“Monitor critical journeys”
Any test can be scheduled as a recurring production probe to watch uptime, journey completion, and p95 duration for important user flows.
Frequently Asked Questions
Where do my tests live?
Tests live in your repository as `.blop.ts` files. They are version-controlled, code-reviewed, and editable or deletable by your team.
Is there a free trial?
Yes. Every plan starts with a 7 day free trial, and the trial includes full access to the features in the plan you choose. No credit card is required to start.
Do I need to host my own runners?
Blop runs through your existing GitHub Actions runners, either cloud or self-hosted. The control plane does not execute tests itself.
Does it only work with Playwright?
Blop is Playwright-first today. The result payload is a versioned contract, and the site says adapters for other frameworks are planned next.
How does the agent fix failing tests?
When a run fails, the agent inspects the failure, trace, and diff, then can open a pull request with a scoped fix and verification build. Auto-fix is in early access and nothing merges without approval.
Quick Facts
- Category
- Developer Tool
- Primary use
- Browser testing and QA automation
- Execution model
- Runs in your CI with GitHub Actions runners
- Test format
- .blop.ts files in your repo
- Framework
- Playwright-first
- Pricing
- Per-user plans with a 7 day free trial
blop Traffic Analysis
Traffic data is for reference only.
- Domain Rating
- 8
blop Alternatives
Hacktron AI
hacktron.ai
AI code review and application security for finding exploitable vulnerabilities in pull requests
cubic
cubic.dev
cubic is an AI code review platform for complex codebases. It helps teams catch bugs in pull requests and scan repositories for issues before merge or release.
Hoplite
hoplite.sh
Hoplite is a coding agent platform that runs work in isolated dev environments and can open pull requests when tasks are complete. It is designed for teams that want to delegate repository work to agents with live feedback and approvals.
cubic
mrge.io
AI code review for pull requests and codebases
AutonomyAI
autonomyai.io
AutonomyAI is an AI-native product delivery platform that helps product managers and designers turn ideas into production-ready code changes in their existing codebase. Engineers review and approve the resulting pull requests before merge.
TeammateX
www.teammatex.dev
TeammateX is a self-hosted AI teammate for software teams. It learns repositories from GitHub, builds searchable code and ownership knowledge, answers with file-and-line evidence, and can create pull requests.