Often people who don't know software testing inside out don't grasp that you can't just change a line of code, test it and then release the product. I remember a one line bug that was fixed but an intel development team. It was an easy fix. They tested the change but ignored the "golden rule" in the book of software testing and released the product. The change they made had a knock on effect and caused a fatal bug in a completely separate piece of code. It was hundreds to one against, but it happened. The worst part was that it only became apparent months later after it had caused millions of dollars of damage to projects all over the world. intel's reputation was badly damaged, the product destroyed. intel sacked the entire development team.
I have no clue who you were referring to by mentioning those nice words from the above: "Often people who don't know software testing inside out don't grasp that you can't just change a line of code..."
Maybe not all the people in this thread could be classified as "really don't know anything abut software testing..."
I personally work since 2014 in software testing and gathered a lot of experience over the years from that (so please be nice when addressing to the public)
NO one says change a line of code and that will fix all the issues in the firmware
All in all, nice story about the fatal bug
The golden rule is - when a product is tested, don't just test what you think you need to test - test it all! That's why it's so slow to test even a simple change. And it's best to save a number of fixes up to justify the time spent testing. All in all, it just takes far more time than you would think.
Go tell your boss you will need more time that he can imagine and see what happens
That's why you have to obey another golden rule in order to test SMARTER not HARDER.
GO GO test automation!