software-testing 9

My post “Add a Verify Button” has a problem. When Rohit requested hyperlocal news for every PIN code in Mumbai, we’d need a “verify” button on every Statoistics card - hundreds of PIN codes, every day. Verifying every output introduces new bottleneck: a person inspecting every unit. That’s 100% inspection - which you do when you don’t yet trust the process. Manufacturing solved this a century ago. At Western Electric’s Hawthorne Works (famous for the Hawthorne Effect), quality control meant inspecting finished products and pulling the defective ones. Walter Shewhart sent his boss a one-page memo; about a third of it was a control chart. ...

I run AI coding agents inside a Docker container for safety. The setup is dev.dockerfile: builds the image dev.sh: launches the container with the right mounts and env vars dev.test.sh: verifies everything works. I wrote them semi-manually and it had bugs. I had GitHub Copilot + GPT-5.4 High update tests and actually run the commands to verify the setup. Here’s what I learned from the process. 1. Make it easier to review. The first run took long. I pressed Ctrl+C, told Copilot to “add colored output, timing, and a live status line”. Then I re-ran. Instead of a bunch of ERROR: lines, I now got a color-coded output with timing + a live status line showing what’s running. ...

Astral released Ty (Beta) last month. As a prototyper, I don’t type check much - it slows me down. But the few apps I shipped to production had bugs type checking could have caught. Plus, LLMs don’t get slowed by type checking. So I decided to check if Ty can spot real bugs in real code. I asked ChatGPT: Run ty (Astral’s new type checker) on a few popular Python packages’ source code, list the errors Ty reports (most of which may be false positives), and identify at least a few that are genuine bugs, not false positives. Write sample code or test case to demonstrate the bug. ...

Presentations and videos from Google’s conference on test automation at London. I was at the event, and learned a lot.

Facts in Software Engineering People The most important factor in software work is the quality of the programmers. The best programmers are up to 28 times better than the worst programmers. Adding people to a late project makes it later. The working environment has a profound impact on productivity and quality. Tools and Techniques Hype (about tools and techniques) is the plague on the house of software. New tools/techniques cause an initial loss of productivity/quality. Software developers talk a lot about tools, but seldom use them. Estimation ...

How to get Yahoo Mail Beta. Since I’m in the UK, I have it already. It’s excellent. I now actually check my Yahoo mail thrice a week, and feel happy while doing it.

Speaking of bugs, here are some famous software glitches – right from the Patriot missiles misfiring to the London Millenium bridge wobbling. Some links are broken, though. (More glitches and links)

Music helps identify software bugs. I’m sure it can be extended to many other forms of ordered data. DNA sequences, time series, etc.

Google toolbar: experimental features.