Answer the question
In order to leave comments, you need to log in
How to correctly estimate the time for testing?
Question for the tester from the interview. How would you respond to this? There is no more context or explanation (a web application is either a service or a desktop application - apparently it is not specified ..).
Answer the question
In order to leave comments, you need to log in
The first thing to say is that such a question cannot be answered correctly . too vague wording. It's like "how to write code correctly?".
As for the ratings themselves.
As already mentioned above, there is an option with an assessment for testing based on development time. Although with the formula:
I strongly disagree. A more realistic estimate is 0.3 of development time.
The second option is to build on the number of test scenarios.
I prefer to count that way.
1) Estimate the scope of the task.
2) We estimate the approximate number of test cases (checks) for this task.
3) We multiply the number by the approximate average time to complete cases (for the web, this is around 4 minutes, then it depends on the specifics of the industry).
4) We put the risks in 0.66 of the assessment
Well, in general, something like this.
I wouldn't go to work there)
Estimating time in a vacuum is such nonsense. If they send you questions for clarification, send them)
It is very difficult to say something about abstract testing of something.
But quite often the assessment is done approximately according to the following formula: QATime = (DevTime*0.35)*0.3;
Using a formula like this: QATime = (DevTime*0.35)*0.3 - is useful only if there is no system data. A similar question in interviews is only intended to test your knowledge of the formulas or test your stress resistance if you do not know the formulas.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question