I'm not sure they teach that in medical school.
They have to deal with a field that was haphasardly constructed by nature over the course of 4 billion years.
Imagine having to retro-document a code base with 4 billion years of history, created solely by junior developers fresh out of college..
The problem is that PHE's own developers picked an old file format to do this - known as XLS.
Do a SUM and match it against a COUNTIF on another column, or something. It doesn’t really matter what it is but if the data is important at all, I always scatter little checks throughout.
The case described in this article sounds like someone who just doesn’t know how to use Excel. I mean why in the name of VLOOKUP would you override the default and choose to save as .xls? That was a conscious decision. Anyone worth their salt knows that’s stupid.
Excel is not to blame here.
This simple post-condition would have caught this issue: The sheet after merge operation must have a number of rows equal to the sum of number of rows for all merged sheets.
Assuming this is a merge of a standardized input, then another post-condition might be: The number of columns in output shall equal the number of columns in the input. Might want to check header names, and order as well.
Thinking in terms of universal properties, and putting the checks into production, is better than unit-testing.