1.2. Test Management Problems

These are some of the practical issues for Test Management in Software Engineering.

Scenario: Missing documentation

Engineer 1:

I have implementation many tests, but I took shortcuts and did not document test specifications.

Engineer 2:

OMG! How will you find gaps in your testing?

Scenario: Mapping implementation with specification

Engineer 1:

I think I have implemented exactly as it is specified in the test specification document…

Engineer 2:

Are you sure?

Engineer 1:

OMG! We have spent a lot of time in reviewing the test specification, we now have to spend more to review test implementation vs test specification.

Scenario: Test specifications are being re-vamped

Engineer 1:

Lots of test specifications are being re-written.

Engineer 2:

Really? Now we will have to re-write test implementation as well. :-(

Engineer 3:

Improvement is good, but this is an endless cycle. :-(

Scenario: Development has not yet started

Tester:

Hey developer, when are you going to start developing this new feature?

Developer:

Not any time soon. I am still busy with other work.

Tester:

OK. Can you please give me some stub implementation to start with?

Developer:

Sorry… Extremely Sorry. I will have to think very hard to create meaningful and functional APIs. I can’t help you straight away.

Tester (Thinking):

(The developer has not started. What can I do right now?)