10. The tester’s task is easy: he should merely
write and execute the test cases by translating requirements to test cases.
Additionally log some bugs.
9. Every test case is documented. Otherwise, how on
earth can we expect to do regression testing and in general repeat testing?
8. Test case Reviews are a one-time effort. All you
have to do is take an artifact after it is completed, and verify that it is
correct. Test case reviews, for example, should merely verify that *all*
requirements are covered by test cases and EVERY REQUIREMENT is COVERED by AT
LEAST ONE TEST CASE.
7. Software Testing should be like manufacturing.
Each of us is a robot in an assembly line. Given a certain input, we should be
able to come up automatically with the right output. Execute a set of test
cases (should execute 100 test cases a day) and report pass/fail status.
6. Software Testing has nothing to do with
creativity. Creativity – what? The only part which requires creativity is
designing your assembly line of test case design. From that point on, everyone
should just be obedient.
5. Creativity and discipline cannot live together.
Creativity equals chaos. [This one remains unchanged from original list of
software development myths]
4. The answer to every challenge we face in the
software industry lies in defining a process. That process defines the assembly
line without which we are doomed to work in a constant state of chaos. [BIG ONE
…This one remains unchanged from original list of software development myths]
3. Processes have nothing to do with people. You
are merely defining inputs and outputs for different parts of your machine.
2. If a process is not 100% repeatable, it is not a
process. Letting people adapt the process and do “whatever they want” is just
going back to chaos again.
1. Quality is all about serving the customer.
Whatever the customer wants, he should get. Things that don’t concern your
customer should not be of interest to you.
