When does testing start?
I am currently working in a team of testers in a quite big project. It should be noted that the project size and process limits my personal scope and the things I can really change. The test team has not been there for very long, and our environment responsible s haven’t yet gotten the test environments completely up. One reason for that is that some parts of the system have not been completely delivered just yet, so the possibility to test the functionality flow is limited. But when do we start testing?
A developer that has helped us getting some of the environments in place asked me when we are going to start testing those parts, which he has been developing. I have worked with him before, and I know he is a good developer that has really understood that testing provides him with feedback.
-“We are already testing” I told him.
-“But the test environments are not up yet?”
-“No, but at the moment we are testing the requirements and the documentation that really exists”.
For the developer, who is really used to testing being his way of getting feedback on his work, this answer did not really satisfy him. At the moment we are really not giving him feedback, but other parts of the project that deliver the requirements and documentation.
Since we have gotten his involvement in getting some of the environments up, it is a real bugger that the rest of the software has not been delivered yet. And until that release, we cannot really “start testing” his parts, in the sense he thinks of testing. Instead we have been bothering him to finish up and deliver his documentation, which is of course also a deliverable to test.
Of course, the product under test is really the code. But until delivered, testers can do no better than work with the material available and provide good information about the status of the product that way. Do you agree or disagree?
When does YOUR testing start?