AI Test Engineer by BlinqIO
Playwright code + self-healing tests w/ no vendor lock-in
453 followers
Playwright code + self-healing tests w/ no vendor lock-in
453 followers
BlinqIO’s AI Test Engineer builds and maintains Playwright automation in minutes - generating real code in your repo, integrating with CI/CD, and self-healing when your app changes. No lock-in, just faster, stable, zero-touch testing.
Hi Product Hunt - Big update from the BlinqIO
Three months ago we launched BlinqIO on Product Hunt as an AI Test Engineer for Playwright.
Since then, we’ve worked closely with engineering and QA teams - and rebuilt major parts of the product to make Playwright testing truly intuitive and autonomous.
Here’s what’s new:
AI Recovery & Autonomous Maintenance
Tests now detect UI changes and recover automatically.
Fixes broken locators in real time
Suggests and applies maintenance automatically
Reduces flaky tests and maintenance overhead
One of the biggest things we learned after launch:
Test maintenance is still the biggest bottleneck in Playwright automation.
So we decided to eliminate it.
AI Chat + AI Recorder
You can now create Playwright tests in the most natural way for you.
With AI Chat you can:
Describe intent naturally
Point to UI elements while chatting
Add validations like:
“Verify error message appears”
“Check total is $100”
AI understands the context and generates the full Playwright test automatically.
Prefer showing instead of describing?
Use the AI Recorder for complex flows, forms, and precise interactions.
Or combine both seamlessly.
AI Test Ideas from Jira
Testing now starts when the ticket is created.
AI can generate test ideas directly from Jira tickets to help teams keep coverage aligned with development.
Freemium Upgrade
We expanded the free plan from 5 → 20 scenarios so teams can try real workflows with full AI capabilities.
The product we launched 3 months ago is not the product we have today.
Would love feedback from the Product Hunt community - especially from engineers, SDETs, and Playwright users building modern testing workflows.
Try the upgraded AI Test Engineer:
https://blinq.io/
Hi Product Hunt - Big update from the BlinqIO
Three months ago we launched BlinqIO on Product Hunt as an AI Test Engineer for Playwright.
Since then, we’ve worked closely with engineering and QA teams - and rebuilt major parts of the product to make Playwright testing truly intuitive and autonomous.
Here’s what’s new:
AI Recovery & Autonomous Maintenance
Tests now detect UI changes and recover automatically.
Fixes broken locators in real time
Suggests and applies maintenance automatically
Reduces flaky tests and maintenance overhead
One of the biggest things we learned after launch:
Test maintenance is still the biggest bottleneck in Playwright automation.
So we decided to eliminate it.
AI Chat + AI Recorder
You can now create Playwright tests in the most natural way for you.
With AI Chat you can:
Describe intent naturally
Point to UI elements while chatting
Add validations like:
“Verify error message appears”
“Check total is $100”
AI understands the context and generates the full Playwright test automatically.
Prefer showing instead of describing?
Use the AI Recorder for complex flows, forms, and precise interactions.
Or combine both seamlessly.
AI Test Ideas from Jira
Testing now starts when the ticket is created.
AI can generate test ideas directly from Jira tickets to help teams keep coverage aligned with development.
Freemium Upgrade
We expanded the free plan from 5 → 20 scenarios so teams can try real workflows with full AI capabilities.
The product we launched 3 months ago is not the product we have today.
Would love feedback from the Product Hunt community - especially from engineers, SDETs, and Playwright users building modern testing workflows.
Try the upgraded AI Test Engineer:
https://blinq.io/
More information and tutorial video here: https://www.docs.blinq.io/
AI Test Engineer by BlinqIO
@barmeir_tal Exciting to see how much BlinqIO has evolved since the Product Hunt launch.
One of the biggest things we hear from QA and engineering teams is that creating tests is only part of the challenge. Maintaining them as the product changes is where teams lose the most time. That’s why updates like AI Recovery, autonomous maintenance, AI Chat, AI Recorder, and Jira-based test ideas are so important. They help teams move from simply generating Playwright tests to actually keeping testing aligned with real product changes.
Learn more about it here!
tutorial video here: https://www.docs.blinq.io/
This is a strong take on a very real problem.
E2E tests usually fail not because the logic is wrong, but because maintaining them becomes a full-time job as the UI evolves.
Generating real Playwright code in the user’s own repo + no vendor lock-in is a big trust signal — that alone removes a lot of friction for adoption.
Curious about the self-healing part: when selectors change, how much is rule-based vs model-driven, and how do you avoid masking real regressions?
API testing support sounds like a natural next step. Congrats on the launch 👏
Finally a tool that treats flaky E2E tests as a code-gen problem, not a human debugging marathon! Love that the generated Playwright lives in my repo—no black-box lock-in and I can still npx playwright test on CI. Two quick questions:
Does the AI auto-heal only selectors, or can it also patch waits/assertions when latency spikes?
If I run tests on a private staging env behind VPN, will the BlinqIO cloud agent tunnel back to my network, or do I have to run everything locally?
Looking forward to stress-testing it against our most chaotic sprint. Congrats on shipping true vibe testing!
@haf_zhang Thanks for the thoughtful note.
On healing: BlinqIO’s AI healing focuses on element selectors and UI structure changes. It helps keep tests stable when the DOM shifts, without requiring manual updates. It does not auto-patch waits or assertions in response to latency or timing variability - those are still authored and tuned by the team.
On private staging behind VPN: if your staging environment is not reachable from the public internet, you would run tests locally or within your own CI/CD environment that has access to that network. The product does not create a cloud tunnel back into private environments. Tests are real Playwright, so npx playwright test (or CI runners) work fine inside your own network perimeter.
We are happy to support your stress testing if needed.
AI Test Engineer by BlinqIO
Hi everyone, I’m Rebecca from BlinqIO.
I’ve been part of the team preparing today’s launch and working with the team developing the NEW version of the AI Test Engineer. A big part of this release is Vibe Testing starting with intent and making automation easier to adopt in real teams. We’re excited to share it here and hear your feedback!!
Congrats team @sapnesh_naik @liat_niederman @barmeir_tal
Wingman Studio
How do you support modularity and reuse across multiple teams or projects?
@david_sipos we do not replace your architecture -we generate Playwright that fits into it, so modularity and reuse work the same way they do for the rest of your code.
BlinqIO leans on real Playwright code and your existing repo structure to support modularity and reuse across teams and projects.
The AI generates standard Playwright tests, so you can organize them into shared helpers, page objects, and libraries like any other codebase.
Because everything lives in your own Git repo, teams can reuse patterns via shared packages, monorepos, or templated projects rather than being locked into a proprietary test model.
You can also plug the generated tests into your existing CI/CD pipelines, so different teams can own their services while still sharing common utilities and conventions.
Vocably (a language-learning tool)
Nice idea!
@sneas Thank you Dimah!