1000 Errors, One Google Sheet, and Five Hours I Will Never Get Back

Every bug has a story. Most start with the phrase: "It works on my machine."

We were testing a data import feature for a lead generation company. The feature seemed simple. You click an import button, upload a spreadsheet, and the system loads the contacts. Everyone assumed it worked.

That assumption is a trap.

Testers exist to ruin that assumption. The "happy path" always lies to you.

If we used a clean Excel file, the import passed. We could have gone to lunch. We could have shipped the feature. But a customer would have found the bug on a Monday morning in production.

The problem was a Google Sheet.

Real users do not use clean Excel files. They use messy Google Sheets. They expect systems to handle their chaos.

When we uploaded the Google Sheet data, the system failed. We saw over 1,000 errors. The screen filled with errors. The same button and the same data type caused a total collapse just because the source format changed.

We went back to Excel to test more. We tried a mix of valid and invalid rows. The system handled it well. It skipped the bad rows and moved on.

Then we tried real-world chaos. We uploaded a bulk file with hundreds of rows. Most were garbage. Only a few were good.

The system broke completely. The validation logic worked for a few bad rows, but it died under a mountain of bad data.

We spent five hours finding the root cause. We stared at screens, re-ran tests, and blamed the files, the browser, and the coffee.

Those five hours were cheap. The alternative was a customer losing their afternoon and losing trust in our product. You pay for bugs in testing with time. You pay for bugs in production with customers.

I will choose the five hours every time.

A good tester does not ask if a feature works. A good tester asks how to break it.

Stop thinking like a developer. Start thinking like these people:

  • The lazy user who uploads the wrong file format.
  • The chaos user with merged cells and empty rows.
  • The bulk user with 4,000 dirty records instead of 10 clean ones.
  • The troublemaker who does exactly what they should not do.

Software breaks on the inputs you did not expect.

The most "simple" features are often the most dangerous. The import button, the search box, and the contact form look harmless. They are not.

If a feature passes the happy path, do not move on. Be the person who asks: "What if I upload the worst file imaginable?"

Then go do it.

Source: https://dev.to/jaswanth_m_ab71bf22ec8b0/1000-errors-one-google-sheet-and-five-hours-i-will-never-get-back-4okl

Optional learning community: https://t.me/GyaanSetuAi