... reviewing an agent's work on a bug fix. Clean diff, passing test, looked fine. Something made me suspicious. So I reverted the fix and ran the test

... agent had a failing test. It "fixed" it in about ninety seconds. I almost moved on. Then I looked at the diff. It hadn't touched the application code. It had changed the test

... agent wrote a fix for a bug and included a passing test. I was suspicious, so I reverted the fix and ran the test

... agent wrote a fix for a bug and included a passing test. I was suspicious, so I reverted the fix and ran the test

... been leaning heavily on AI assistants to ship entire features in record time, but my test coverage is lagging behind badly. Whenever I prompt the AI to write unit tests

... take, but I take it back lightly: The more writing is done by the assistant for your project, the more your tests weigh as your knowledge of the code fades away. For example, for a recent application to split expenses between friends, I let the assistant write the logic while creating three tests

... After the third time an agent gave me a passing test that was testing

... Whenever I let an agent implement a new feature, it either writes brittle tests that pass by mocking everything out of existence, or it outright deletes existing integration tests

... give a text generator six different voices (a dry friend, a drill sergeant, a corporate manager, and so on). Every prompt carries shared rules: word count, how many emojis, where they go, never invent a number. I tested it end to end against a fake model server: 127 checks that the exact prompt reaches the model for every voice, all passing. That proves the prompt is assembled correctly. It proves nothing about whether the model follows it. First real ... ... rule against computing new ratios, tighter length wording, and bigger palettes. I also wrote a preview script that checks eight rules on real output and prints ok or CHECK for each, using the same checking code my unit tests

... agent added a test for a bug fix. I reverted the fix and ran the test

... count as a repeat). The rule itself is small, but time rules go wrong at the edges: exactly at a boundary, two flags a minute apart, a timestamp with microseconds and a +00:00 offset. So I wrote 61 tests, then did something I now do for every rule like this: I broke the code on purpose, seven different ways, and checked that a test

... everyone! We ve released Rentgen v2.0.0 Rentgen tests your API from a single cURL: map your fields, click run, and get validation, boundary, security, authentication, and performance checks. Core testing

... skips the generation, shows a support page, and pauses the feature. The final level is the max of three signals: a phrase filter, the classifier, and a level returned by the generation call itself. I tested it across several sets of typed messages: crisis, sarcasm, jokes, other languages. Then, while testing

... Last week I gave Claude Code the task of fixing a broken checkout test in my little Next.js store project. Within 20 minutes, it came back telling me all tests

... developer. I build by directing AI agents, so tests are how I know something works. I can't check it by reading the code. For a while the green checkmarks were enough for me. They shouldn't have been. Now every bug fix comes with a test

... been testing a safety check for an AI app by running a script of test

... before looking at the code. The variable was never bound to the database. Comment from Konstantin Tikhaev(@konstantin_tikhaev): It hit an API timeout, quietly swapped in a hardcoded mock object, and reported the integration test was passing. A failed run is just debugging. Passing on fake data means the priority is declaring success rather than being right. Comment from Konstantin Tikhaev(@konstantin_tikhaev): The summary report shipped with a confident metric that took a day to act on. Tracing ... ... never been checked. Around 6,700 lines gone, no error anywhere.. Comment from Farzam(@farzam_habibi): @neelagiri_chettiyar  It was pushed and deployed, but we haven t released it to users yet.. We want to run more tests

... shipping an AI chatbot or agent and don t know where to start with security testing, I built five free tools in PromptBrake to help. Get prompt-injection inputs to try, map risks to test

... Something I keep running into with vibe coding: the agent makes a failing test pass by loosening it instead of fixing the code. One example: it replaced a strict deep equality check with expect.anything() on an error payload. The test

... That's enough to write the record myself and hand it to a fresh CWNetwork: func network(_ record: [String: Any]) -> CWNetwork { let network = CWNetwork() network.setValue(record as NSDictionary, forKey: "scanRecord") // private: probes and tests only return network } func rsn(_ akms: [Int], mfpRequired: Bool = false) -> [String: Any] { ["IE_KEY_RSN_VERSION": 1, "IE_KEY_RSN_MCIPHER": 4, "IE_KEY_RSN_UCIPHERS": [4], "IE_KEY_RSN_AUTHSELS": akms, "IE_KEY_RSN_CAPS": ["MFP_CAPABLE": 1, "MFP_REQUIRED": mfpRequired ... ... SCAN_RESULT_OWE_MULTI_SSID = 1 (the open half of a transition pair, judging by its name) comes back yes to .OWE too. So .oweTransition wasn't needed for anything. The fix is small; the lesson is in the tests

... maker of dotpals (a small open-source pal that shows what your AI coding agents did). Most people seem to use Jev for lead-gen and booking calls. I'm using it for something different: as a judge for test results. My coding agent says "All tests

... situation: the system works, yet no one fully understands how it works. That makes me wonder whether some of the most useful techniques for vibe coding are actually techniques we already use for legacy systems. For example: Snapshot / approval tests: capture the current output and require explicit approval when it changes. Characterization tests

... Everyone says to test demand before you build. We didn t. We built the product first, like a lot of people do, and only afterward found a fast way to test

... Software testing is becoming harder as applications grow across web, mobile, APIs, and enterprise systems. Traditional testing

... launched CoWork, a mobile app testing solution, on PH a while back and got a lot of useful feedback. Some of the most interesting comments came from developers who wanted to test