Thursday, September 22, 2016

Murphy's Laws of Software testing

Taken from my facebook wall. Here goes:

1) Bugs can easily be created. They cannot however, be easily destroyed. But they can easily get transferred from one platform to another.
2) There is no such thing as a bug free application. But yes, bugs do come free with every application. :)
3) Bugs do not get reproduced when you demo them to the developer / project manager.
4) But will magically reappear from nowhere when you demo your product to the client / customer.
5) Your most bug-free product version will reside in your developer’s local machine / session. Bugs never happen there.
6) The more the number of developers working on the product, the more bugs there will be to find.
7) Bugs which have been deemed fixed and closed always reoccur in Production.
8) No matter how extensive your test coverage is, you will always miss / overlook one aspect of the product.
9) And that’s where the bug will usually occur in production.
10) No matter how many critical bugs you find, you will be pilloried for the one bug you failed to detect.
11) The PM and delivery manager will always consider the testing team as dead weight.
12) The bug which takes the maximum amount of time to reproduce will always take the least amount of time to fix.
13) The bug which causes the maximum amount of damage always requires the smallest of fixes.
14) Customers / End users usually find more bugs than your testers’ do.
15) Bugs will never be apparent if you keep looking for them, but when you are not, they will pop up from every nook and corner of the application and will hit you in the face.
16) Automation might get things done quicker, but the amount of time it takes to script the tests and run them will make you think of running the tests manually.
17) The most critical and time consuming bug for the developers to fix will always occur at the fag end of the testing cycle or when the product is ready to ship.
18) You will spend a huge amount of time and energy in detecting a bug only to find that it now not reproduced.
19) Even if you do reproduce the goddamn bug and file it, it inadvertently turns up not to be in scope.
20) Even if it is in scope, someone else would have already filed it a long time back.
21) The product / feature for which you have detected the maximum number of bugs will most certainly be de-scoped.
Developers’ ultimate justification for bugs:
“But it does not happen on my local machine!!” :)
"This issue is not in scope."

Murphy’s Ultimate Law of all products:
“It just won’t work!”

No comments:

Post a Comment