7. The testing process

The testers follow the plan exactly. They enter the data just as it is shown in the plan and then they record what happened and whether the test passed or failed.

If the test was passed they go onto the next test. If it failed they fill in a form to tell the developers that they need to look at that part of the system again.

The testers normally take screen shots of every test to provide evidence of what they have done. These can be referred to by the developers if they cannot replicate the problem. They can also be used by an audit team at the end of the project to check that the testing was done properly.

This stage may seem to you a bit pedantic - after all why couldn't the developer have run this test when they were coding the software and then fix it instantly? - Answer: Human Nature!

It is a very bad idea to have the person who codes the software to test it! This is because they know too much and so will tend to make assumptions about how real users will use their software.

The best testers are those who know nothing about the system and will do things to the system the developer never imagined! Just like real users!