Your test suite is green. Your users still hit the bug.
Why scripted automation keeps missing the failures that actually cost you users — and what testing like a real person looks like. Every engineering te…
Tech news from the best sources
Why scripted automation keeps missing the failures that actually cost you users — and what testing like a real person looks like. Every engineering te…
A few months ago, I was running QA on a fintech platform a customer-facing portal where businesses fund a wallet and spend from it. Every wallet featu…
TestSprite's CLI makes a design choice most testing tools would never advertise: it refuses to do something. When a coding agent asks for a failure re…
Browser testing has quietly become more complicated. A few years ago, most teams were mainly worried about selectors, waits, flaky CI machines, and wh…
When teams start with test automation, they usually ask the tool question too early. Should we use Playwright? Selenium? Cypress? A no-code platform? …
Back to Feedback — Episode 2 of 20 Where it came from This one showed up first as a passing comment from a teammate mid-year: I sometimes seemed to sp…
Android teams often talk about automation as if the choice is simple: run it on an emulator because it is fast, or run it on a physical device because…
Every team has lived this: a pull request looks clean, gets approved, merges — and twenty minutes later the test suite is red. The change was in src/ …
For the past year and a half, I've been building Evaficy Smart Test — a QA platform for manual testing teams that brings AI into the parts of the work…
Most teams still treat manual test cases as rows in a SaaS database. That worked when cases were written slowly, reviewed rarely, and automation lived…
Most browser test suites do not fail because the team forgot how to write a click step. They fail because the system around the tests becomes more com…
AI can generate a test script before you finish your coffee. That sounds like the hard part of test automation has finally been solved. In practice, m…
There is a quiet tax many engineering teams pay after their automated test suite starts to matter. The tests live in code. They run in CI. They alread…
Originally published on the Prufa blog . Five days ago we audited 49 Show HN launches and found that 78% had a critical bug on day one. This week we p…
Software testing is usually described in two large categories: exploratory testing and automated testing. Exploratory testing is about investigation a…
Disposable email feels like a cheat code. Hand the form an address that exists for an hour, get whatever you came for, walk away. No spam. No mailing …
Quick Share and AirDrop-style sharing are useful because they solve a simple problem: a file needs to move from one device to another. That file might…
Web testing has become a lot harder to describe in one sentence. It used to be easier to say, “We run some Selenium tests,” or “We use Cypress for fro…
Most test automation demos are too clean. The demo app is stable. The login flow is simple. The selectors are obvious. The data is predictable. CI is …
Originally published on the Prufa blog . In June 2026 we pointed Prufa's free audit at 50 products that had just launched on Show HN — every launch fr…
Frontend testing has become weirdly broad. A few years ago, a lot of teams treated it as "write some Cypress tests" or "run Selenium in CI." That was …
On one side, it has never been easier to generate tests. You can ask AI to write Playwright code. You can record flows. You can use no-code tools. You…
The biggest mistake teams make when comparing testing tools is treating the feature list like the decision. A tool can support API tests, visual check…
If your goal is faster releases with fewer flaky failures, the tool choice matters less than the testing strategy behind it. Teams usually start by as…
A practical look at the strategies, tools, and trade-offs behind resilient API test automation and why test data management is just as important as th…
Android 16 desktop windowing is useful for larger-screen workflows, but it also creates a practical QA question: does your Android app still behave co…
I remember the first week I seriously used Playwright. I was migrating a 200-test WDIO suite. I thought it would take two weeks. It took four days. No…
I have a confession. For a long time I was a WDIO loyalist. I had built entire frameworks on it, trained teammates on it, and defended it in every "wh…
You just merged an AI-assisted feature branch, the code review looks clean, and the app works in your local smoke test. Now comes the real question: d…
The failure starts small A test that passes 200 times and fails once does not feel urgent. Usually it gets retried, marked flaky, or blamed on CI nois…