Thursday, August 27, 2009

TESTING IN A HURRY!

Suppose the client says that they need the product urgently. It's time to launch. As a tester you have only 2 days to test. What will you do?


This is a challenging situation. First of all this situation should not happen in a well developed software industry however if it happens, then as a tester you need to approach it in a different mannerism.


1) Check which functionality is most visible to the user?


2) Check which functionality is most important to the projects intended purpose?


3) Check which functionality has the largest safely impact?


4) Check which functionality has the financial impact on the users?


5) Which part of the application are more important to the customer?


6) Which part of the project was designed in a hurry?


7) Which aspects of similar projects caused problems?


8) What kind of problems would cause more customer service complaints?


9) What kind of tests could easily cover multiple functionalities?


10) Which part of the project was most complex and subject to errors?




I hope all this information was helpful to you.

No comments:

Post a Comment