and maintainer of:
Test Phases and Deliverables
I got a mail from a panicking project manager. Apparently he had been asked to present how we where to go about testing the project deliverables.
He sent out a test plan to all the involved parties.
The test plan outlined the follow test phases:
And it seemed as if we were supposed to document our tests in the module test phase.
So I wrote back to the project manager and asked what he expected for us to deliver. Since the test plan did not really specify. I reminded him that we were working on different platforms, with diverse tools etc. The Java programmer on the project concurred.
I did think about TAP when reading the response, but did not go into this.
So panick really struck the project manager, he even came by my desk.
So after some explaining he understood that the development was in good hands at least for the programming and configuration side. Since all people involved would test and document in their own format.
A business analyst working for 'Application & System Integration Development' stated that she was taking care of the integration test coordination and execution.
So we succeeded in calming down the project manager and we could go back to work.
So I looked at what I wanted to do and found out that I was not supposed to do any integration with the Java part until the Integration test, so happily I copied the examples from the Java Web service API specification, and mock... mock.. mock my tests are running as if there was a backend.
Man I love Perl and CPAN.
So my complete test suite can be called as if we are doing integration test or not.