Skip to content

I Just Launched The KomSea – And It All Started With a Bug

A Midnight Debug That Changed Everything 20 years ago, when I was a developer writing C code, there was a major downsizing at work. We had lost our test engineers, and I stepped in to do peer testing for a USSD callback telecom feature—back in my Motorola days in Bangalore, India. I still remember theContinue reading “I Just Launched The KomSea – And It All Started With a Bug”

Croissants, Bagels, and Sanity Tests: Why Testing Terms Matter

Disclaimer:  Bagel lovers, please proceed with caution.  This blog post uses a croissant versus bagel analogy to illustrate a point about software testing.  While bagels are delicious and worthy of their own celebratory posts, for the sake of this argument, they represent miscommunication.  We appreciate your understanding (and your love of bagels!). Imagine this: YouContinue reading “Croissants, Bagels, and Sanity Tests: Why Testing Terms Matter”

Testing on Broken Crutches: Surviving Paper Cuts in Automation Tools 

“Why does running one test feel like assembling IKEA furniture blindfolded, with three screws left over?” Testing should be hard because of the system under test (SUT)—not the tools you’re using. Yet, when automation solutions are overcomplicated, unclear, or overly flexible, they create paper cuts—those tiny, maddening problems that pile up until you’re questioning yourContinue reading “Testing on Broken Crutches: Surviving Paper Cuts in Automation Tools “

What Is HIL Testing? Can’t Park a Car At My Desk! 🚗

Back in 2014, when I first stumbled into firmware testing at CSR in Cambridge, UK, I had one simple question:“What’s a GPIO? Is that like a button on the board?” To this day, I swear my then-boss Gordon—with his thick Northern English accent—did a double-take before mumbling something about SPI, I2C, UART, GPIO, SDIO asContinue reading “What Is HIL Testing? Can’t Park a Car At My Desk! 🚗”