Estimation of time for testing is an integral part of a larger evaluation of the project as a whole. This is a complex process that provides, among other things, the customer and the project manager with control over the fulfillment of the formulated tasks. The main difficulty of this type of assessment in the correct planning of the process, there are many methods, but there is no universal method, we will consider the most used ones.
The easiest way to start is to write a clear test documentation, to divide it into thematic information blocks consisting of test case sets. Further, it is necessary to count the time that will be required for each block to pass – here one must be guided by experience and expert judgment, in cases of “impossible” and “do not know”, to make a calculation hypothetically. Separately, I would like to mention the human factor a qualitative plan should take into account vacation and dayoff’s. Devote a separate column “time to fix bugs” and regularly update the information in it. Such a method is usually called the decomposition method, a kind of constructor, which is sorted out to the smallest detail, evaluated and collected back.
I would also like to mention the method of three points. Detailed analysis of the technical assignment and drawing up a competent test plan during meetings within the team members creates the most optimistic forecast of product realization in figures (hours and money). Then the most pessimistic with all sorts of difficulties and delays. Then the obtained values are substituted into the formula:
C = A / B;
E = (A + 4 * C + B) / 6;
where “E” – the most realistic estimate, “A” – optimistic, “B” – pessimistic, “C” – averaged estimate.
Thus, we get the most realistic estimate, in which we have a composition of positive and negative scenarios. After that, based on the data obtained, a work schedule is built.
In general, the estimation process can go from a couple of hours to several weeks – it all depends on the scale of the project and the number of decimal places.