You work as a testing analyst for a software development contractor that has bee

Question

You work as a testing analyst for a software development contractor that has been engaged to develop this enterprise system. If the project is not completed on schedule, your company loses a substantial bonus. Since design and construction ran behind, you will have to cut system testing in half. Your company is putting a great deal of implicit pressure on you to compress testing so the project can finish on schedule and the company will receive its bonus. You have qualms that if testing is compressed, some serious problems may be missed, even with a risk-based testing strategy. What do you do?

Explanation / Answer

Answer) Risk based testing strategy is a technique in which various risks are identified and they are assigned different priorities. On the basis of those priorities, these risks are tested. In the above mentioned case as well, Risk based testing is the only option left. I would have chosen that strategy, identified the various risks, prioritise them and start testing on the basis of that priority level only. The one which has very chances of occurence will be tested first. The risks which have very less chances of occurence are usually skipped as they can be taken care of after the official launch by providing various updates to fix them. So in the provided scenario as well, this is the best suitable case. Reduce the number of test cases, complete the project and than provide updates. This will lead to the successfull completion of the project in time and the bonus will also be given.

Related Questions

Navigate

• Browse (All)
• Browse Y
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.