AI Test Engineer by BlinqIO
Playwright code + self-healing tests w/ no vendor lock-in
477 followers
Playwright code + self-healing tests w/ no vendor lock-in
477 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,
I’m Tal, founder and CEO of BlinqIO - the AI Test Engineer for end-to-end testing.
We’re engineers ourselves, building for the technical community, and we’ve felt this pain firsthand:
test automation is one of the biggest bottlenecks in software release cycles - especially E2E testing.
We built BlinqIO to remove that bottleneck entirely.
BlinqIO introduces Vibe Testing:
An AI Test Engineer that uses GenAI to create, maintain, execute, and analyze end-to-end tests automatically.
Under the hood, BlinqIO generates real Playwright test code, stored in your own Git repository - so there’s no vendor lock-in. You fully own the tests.
The result: E2E testing goes from a constant human burden to an autonomous AI capability, finally unblocking faster, safer releases.
It is free to get started.
What’s next: we’re already working on extending the AI Test Engineer to support API testing.
We’d love your feedback: What other testing areas or workflows would you like us to support next with the AI Test Engineer?
Tal
@barmeir_tal Hi Tal, this sounds very interesting. congrats on the launch. How do you address test planning with this; bugs vs bad test?
AI Test Engineer by BlinqIO
@barmeir_tal @zolani_matebese Thanks for the question! BlinqIO supports test planning through automated test creation, structured test execution, and detailed failure analysis. When something breaks, the platform provides clear diagnostics and AI-assisted root cause insights so teams can quickly understand what happened, why, and where. This helps streamline the decision process during planning and triage by reducing the time spent digging through logs or guessing at failures.
AI Test Engineer by BlinqIO
@barmeir_tal @zolani_matebese During AI Recovery of a failed test, the AI can determine if the failure is due to a UI change or a problem with the test itself (login credentials wrong, step missing, etc). You can also review the fixes made by the AI Test Engineer before accepting them. You can reject a fix and have a ticket be created in Jira for a bug that AI identified.
@sapnesh_naik Thank you Sapnehs
@barmeir_tal Hey Tal, I have been hunting some products in the testing space, hence I am curious about what parts of a real-world test suite are included by default and what usually still needs human refinement? :)
AI Test Engineer by BlinqIO
@barmeir_tal @rohanrecommends In a real-world BlinqIO suite, the AI Test Engineer automatically generates the automation code that performs complex UI workflows, and maintains selectors dynamically when the application changes.
However, human refinement is still needed to define high-level business logic, validate edge cases, and ensure the "look and feel" aligns with brand-specific UX standards. Essentially, the AI handles the heavy lifting of automation, execution, and maintenance, while the human engineer focuses on strategy and and supervising the AI Test Engineer.
FuseBase
Congrats on a long-awaited launch, team @barmeir_tal @liat_niederman @rebecca_villalba @sapnesh_naik
Do tests run locally, or do they go through your cloud? Asking from a security perspective.
Hi Kate
Both options are supported - local execution and cloud execution - and you choose based on your workflow.@liat_niederman @rebecca_villalba @sapnesh_naik @kate_ramakaieva
ThankThank you, excited to finally share it
AI Test Engineer by BlinqIO
@barmeir_tal @liat_niederman @rebecca_villalba @kate_ramakaieva
You have full flexibility in determining where you want your tests to run.
Locally on your laptop
Recommended - On the BlinqIO Execution Cloud (Support parallel runs, AI Recovery, Failed test retries, and videos/traces for failed tests).
External CICD/Servers - You can run it on your own third party CI-CD like Github Actions, Jenkins, Azure, AWS etc or any Windows/Mac/Linux server enironment.
Hope this helps!
Sapnesh
@sapnesh_naik Thank you!
Chatscout by Zevi
Does the AI recommend which tests should be prioritised based on risk or production usage data?
@hiya_chaplot1 Thanks for the question. The AI Test Engineer does not prioritize tests based on risk models or production usage data. Today the focus is on generating, maintaining, and executing real Playwright tests, and letting teams decide prioritization based on their own context. Happy to share more if you are curious.
AI Test Engineer by BlinqIO
@hiya_chaplot1 We also have a new feature coming soon that will let you connect your Jira project to BlinqIO so that the AI Test engineer can suggest test cases for tickets that you select. This will be released in the next two weeks!
Logtime
Congrats on the launch! I’ve been using BlinqIO and it’s been impressive. It intelligently updates test scenarios when the UI changes. It’s a real time-saver for creating and maintaining automated tests and speeding up QA. Vibe testing is here 😎
@max_feels Thank you Max for the feedback. Vibe testing is defenetly here
AI Test Engineer by BlinqIO
Tests that write themselves? Hold my coffee
Hey everyone
I am Liat, Head of Marketing at BlinqIO. For the last year our team has been building something called the AI Test Engineer. It started as a small idea and turned into months of talking with testers, breaking things, fixing things, and trying to figure out what actually creates value in real QA teams.
The main challenge was finding the right product market fit in a space that moves fast and has strong opinions. We did not want to add another shiny tool that creates more work. We wanted something that feels useful on day one, respects QA as a profession, and removes some of the pain around automation, coverage, and maintenance.
Along the way we learned what matters most to the people using the product. Speed without chaos. Ownership without lock in. Accuracy without extra complexity. Those values ended up steering the entire roadmap.
Today we are bringing the AI Test Engineer to Product Hunt to get honest feedback from a community that cares about building real products. If you test, ship, or break software for a living, I would love to hear what you think and what you would improve.
Thanks for reading and for being such a supportive community
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
AI Test Engineer by BlinqIO
Hi all!
I’m Sapnesh, Solutions Architect at BlinqIO, and I’ve spent most of my career in the test automation space, thinking on how best to tackle the gap between “tests we want” vs “tests we can actually maintain.”
UI test automation breaks not because teams don’t know how to write tests, but because keeping them running over time is expensive, fragile, and mentally draining.
So we built the AI Test Engineer to work the way real engineering teams work.
From a technical standpoint:
BlinqIO generates real Playwright code using the AI Recorder
The code lives in your Git repo, runs in your CI, and can be edited in VS Code like any other test.
AI Recovery fixes your failed tests: understanding intent, mapping UI changes, recovering broken selectors, and analyzing failures
No vendor lock-in. You can export the code and run it on its own without BlinqIO
Full freedom to edit/change code - you edit/modify the code if you want to. In fact, you can chat with our AI Test Engineer to implement custom code changes!
We also provide our own BlinqIO execution cloud where you can run tests in parallel, with AI Recovery, retry failed tests, get failed test videos, Playwright traces, and more! - You don't need a third-party cloud service to run your tests.
We call this Vibe Testing, starting from intent and letting AI handle the repetitive, failure-prone parts of automation while engineers keep ownership and control.
Please share your questions and opinions here, and I’d be happy to answer them!
- Sapnesh