Thread: How should I estimate the time testing?

What happen when testing time is given one day for a huge application (I know that very less quality work can be done on less period of time) but in such condition what QA should do?

How should I estimate the time testing? What would be the criteria or checkpoints for estimation of time?

for your first question I would like to say that you should target the important , crucial areas where in the risk lies the most. Atleast do a smoke test , then cover happy paths for each and every functionality.

As far as the estimates are concerned - it depends upon factors like , wht is being tested and at what depth. if it is something new then take into account the learning curve. Some historical data for the projects in past can help u base ur future estimates.

use 'divide and conquer" approach , small components are easier to estimate
b ready with optimistic(min days) and pessimistic(max days) estimates.
the ability to estimate is critical.

Originally Posted by kamalsingh

for your first question I would like to say that you should target the important , crucial areas where in the risk lies the most. Atleast do a smoke test , then cover happy paths for each and every functionality.

As far as the estimates are concerned - it depends upon factors like , wht is being tested and at what depth. if it is something new then take into account the learning curve. Some historical data for the projects in past can help u base ur future estimates.

use 'divide and conquer" approach , small components are easier to estimate
b ready with optimistic(min days) and pessimistic(max days) estimates.
the ability to estimate is critical.

nice answer can u tell me about "Performance Test Requirements"
plz dont say it depends on company or project...........i want to about
performence testing also very important for me