Test Estimation Techniques - Test Estimation Template-Test Estimation Interview Questions-Estimation

[@QA1]

Try my new Agile test estimation tool 🛠, based on well-known test estimation techniques: inderpsingh.blogspot.com/2023/10/test-estimator.html No sign-up required and it's free 🆓.

[@kaushikmishra2167]

इंटरनेट पर उपलब्ध सर्वोत्तम विडियोज़ में से एक। आपकी शिक्षण शैली अद्वितीय है। शायद ही किसी और वीडियो में इतने अच्छे तरीके से अनुमान (estimation) प्रक्रिया सिखाई गई है। बहुत बहुत धन्यवाद और शुभकामनाएं।

[@pn21ambekar]

Your explanation is very clear to understand, thanks for the whole series for manual testing, it is bundle of knowledge for all the testers from one source.

[@nageswararaogarine6246]

Wonderful job and perfect explanation. It is very useful even for beginners

[@yogeshwarn8214]

Very nicely explained.Thanks😊

[@QA1]

@yogeshwarn8214 - You're most welcome! Additionally, you should view the comprehensive Test Lead Interview Questions and Answers at kzbin.info/www/bejne/g6SXhqiMnqqpp6s

[@Prakharjainmca]

This video is really great and give good knowledge of Test Estimation.

[@niveditadassap]

Highly appreciate all the effort you have put into all the videos and the way you explain is too good. Keep up the good work going on. Cheers!

[@QA1]

Many thanks, Nivedita.

[@mmustafeez]

To my knowledge this is best available video on software test estimation on KZbin.. Great job done.. Excellent Explanation.. Thanks- Mohammad

[@QA1]

Mohammad Mustafeez ur Rahman Really glad to get such appreciation. Many many thanks to you.

[@helenkbel]

Thank you very much for such a comprehensive clear explanation.

[@goshar17]

Very well explained all the concepts

[@QA1]

@Sharada Gopinath - Thank you! In order to learn something new in Software Testing every day, check out www.youtube.com/@QA1/community

[@vagdhan]

Perfection to the max in the Realistic, Factual Test Estimation Presentation!!! Thanks a ton Inder Ji!!

[@QA1]

Hi Vagdhan, very glad that you liked this video. Many thanks for your comment. Inder.

[@zakirazakira6951]

Beautifully and clearly explained by you.thank you so much sir

[@raagasmilu]

Thanks a lot, its really helpful and added value to my estimation skill

[@mohammedalam5475]

This video is really helpful for understanding the concept. Thanks a lot.

[@QA1]

Mohammed Alam You are welcome. Thank you for your comment.

[@paedrufernando2351]

Excellent clarity of though process .Thanks for helping to understand the perspectives of Test Estimation.

[@QA1]

+paedru fernando Hi Paedru, thank you for your comment.

[@harshaworld]

Hi Sir, you are Awsome and ur explanation is simple and easy to understand thank u so much..keep going....

[@QA1]

Harshavardhan Ece Many thanks for your support. Appreciate your comments :)

[@rashubhardwaj3053]

very informative and simple to understand. Thanks for sharing.Highly appreciate your efforts.

[@dhjgfdg]

Very goods lectures, thanks for the insight)

[@rashmisrivastava9587]

Thanks much for such neat and clear content. Value added to my knowledge. Keep up the good work.

[@QA1]

Thank you, Rashmi.

[@bhartiagarwal1304]

This video is helpful for understanding estimation.Thanks for sharing.

[@reenasharma6188]

Thanks a lot ,it really added value to my estimation skill

[@srit6124]

some questions that i have are:1. Measurements or time factors to get the system Integration time,total integration time,test design cycle time, integration cost?Based on which parameters you will estimate the total time (other than the scope)?////2. what data gather before test effort estimation?3. Change in reqmnts--> how do you reestimate? Thank you

[@Yardsandfeets]

Thank you for the videos,it is really worth and useful. I really appreciate for efforts

[@santos122122]

Thanks!

[@QA1]

Invertigo, many thanks to you for sending this money! It'll help a lot! Best regards, Inder P Singh

[@prabhashankark]

Thanks a lot the presentation is really good

[@QA1]

Appreciate your comment. Thank you :)

[@RahulJain-rn4qo]

Thanks... its very informative and practical...!!!

[@QA1]

@Rahul Jain - Thanks. The WBS is a good test estimation approach IMO. You may want to view my video, Test Lead Interview Questions And Answers at kzbin.info/www/bejne/g6SXhqiMnqqpp6s

[@fauzanofamiluthfi]

very appreciate this video sir.. for me is very useful.. cause I still a junior tester so a lot of testing concept must be learn.. :D

[@chandramouli7662]

hello singh, very nice video on test estimation techniques...Thanks for uploading and educating us..small thing that we missed here is time calculation for test cases preparation for the requirements..

[@QA1]

Thank you, Chandra. Actually, I implied that the test case preparation time is included in "Testing of n requirements" task.

[@tahiraaaasif8602]

. Could please guide me about QA testing and Test case development time during SDLC?

[@eversunnyguy]

Fantastic...i never found this good info on the web. THis guy knows what he is talking in all the videos. I would like to know the background of the presenter. (obviously lot of experience)

[@QA1]

Hi Sunil, I am a test automation architect and software testing professional. Yes, I do have about 20 years experience in the software industry (software development, testing etc.). You can see my profile and connect at plus.google.com/+InderPSingh Many thanks for your comment. Hope that you find this channel useful. Inder.

[@9912449996]

Nice post on estimation..Thanks ..

[@QA1]

Thank you.

[@chinnikrishnad6736]

Thanks a lot singh(Guru jeee), Very nice,clear explaination. I request you to please post a video that how to create a test plan specifically for automation testing project where a list of manual test cases are available.

[@QA1]

Thank you. I don't have a video on this topic but you may find some useful material in the Test Automation strategy section in my blog post at inderpsingh.blogspot.in/2013/03/ExampleTestStrategy.html

[@chinnikrishnad6736]

Thank you

[@sssaamm29988]

Hi All, I am working in a agile project. We were never asked to prepare any kind of such estimate documents. Typically the release date will be given and the number of sprints are also fixed. we have to test stories in the sprint and once the sprints are completed. we plan for a regression testing and E2E testing between the interfacing apps. And the project goes on for months sometimes years. We do story point estimation for the backlog items. my question is when do we need to prepare such time of estimate documents? Is this applicable in agile?

[@ankitdubeyindia]

nice sir,thank you

[@rajpally6067]

really helpfull , thanks for the effort

[@akbarhussain3591]

Thanks , for providing an excellent clarity on Test Estimation..., and i have one question .Do all the companies follow the same testing estimations technique... or let me know which one is mostly used test esti. tech... Thanks

[@QA1]

Thank you for your question. No, different organizations follow different estimation techniques or their variants or combinations. WBS (Work Breakdown Structure), whose example I showed in this video, is widely used per my knowledge. Also, if we can easily revise the estimate in the future, we may go for a high-level estimate (less accurate). If the estimate fixes the resources, we should go for a detailed estimate (more accurate).

[@akbarhussain3591]

Thanks for reply and query clarification...

[@vagabond_boots]

Nicely put together....thankyou

[@QA1]

Nevel, thank you.

[@sahasra8173]

Very nice video. Thanks for such informative knowledge share. I have one question regarding re-testing due to requirement correction or changes - In case of Scrum model, we divide requirements into tasks and changes to requirement is considered as new requirement(?) in such cases what factor we should use for multiplication? I understand that we need to talk to product manager to understand how stable the requirement to come up with estimation factor. In your experience how you deal with this factor in Agile methodology?

[@QA1]

Hi Subrahmanyam, requirement stability is an important thing in case of waterfall type software development life cycles. This is because any requirement changes may affect one or more phases downstream. Changes done later in the life cycle affect more tasks. In the iterative type software development life cycles, if the requirement changes are treated as new requirements, please refer my explanation on "Testing of n requirements". The estimation factor (T2 in this video) should depend on the requirement detail (less time if the requirements are detailed and more time if the requirements are higher level). Thank you. Regards, Inder P Singh

[@manasbarik5301]

HI, Is your estimation is for the test execution related activity. or it also include the time for planning also (like Requirement understanding + Test Cases Writing + Test cases review + Test data preparation) . I mean the 30 minutes that use put is for Planning + Execution.

[@QA1]

Hi there. In this example, I have mentioned 0.5 to 4 hours per requirement for all these activities (requirement review, test design and test execution) but excluded negative testing, exploratory testing, logging of defects, re-testing and regression testing (these are estimated separately). Depending on your process, you may need different factors, T1, T2 and so on.

[@AbsolutelyNOW]

Great content.Thank you

[@QA1]

@musicrockersmetal99 - Nice to know that you are interested in Test Estimation. WBS gives us more accurate estimates. Thank you. Inder P Singh

[@gauravpranesh1537]

Neatly explained, thank you.

[@QA1]

Gaurav, thank you for your comment.

[@ritu7180]

Thanks a lot for this detailed explaination of test estimation.I have some queries regarding software testing.Give me a point of contact so that i can mail you or phone you..

[@QA1]

ritika ritu Thank you for your interest in my videos. Sure, you can send me a message on Google Plus at plus.google.com/+InderPSingh

[@arunkumar-yi2ts]

thank you,,,,

[@faidamona8838]

Very useful. Thank you

[@QA1]

Many thanks, Faida. Consider viewing my other software testing tutorials at kzbin.info/www/bejne/g6SXhqiMnqqpp6s

[@QA1]

All my Test Design Techniques tutorials are available at kzbin.info/www/bejne/q6rHcqygprmGn9k

[@PremKumar-lq9me]

These video is good can you please share me that excel report with calculation data for understanding

[@norad1090]

Hi Thank you for this great video,I read about some Technics for test estimation such as "three point" & "functional point" is it worth to use them or we can get the same result by using your method for estimation.Thanks in advance.

[@QA1]

Nora D Hi. Yes, each of these other techniques has its own merits. The test estimation technique demonstrated in my video is the activities-based approach/ WBS approach. Though it takes more time to estimate, WBS-based estimates are usually more accurate than those produced by some other estimation techniques. I have explained many relevant points in my blog post at inderpsingh.blogspot.com/2010/03/how-to-estimate-testing-efforts-6.html

[@grapevine5352]

Thaks for video. Excuse for my question - the speeker has Indian accent? It's useful to know the variant of situation in my future job :)

[@QA1]

+Klym Myrvoda Yes. Were you able to understand the voice?

[@grapevine5352]

Yes I were. My English is not exelent so I had to have some time to understand some words. But It was not fast speech, so I had enough time to understand.

[@QA1]

+Klym Myrvoda Thank you for your valuable feedback. I will try to speak all words clearly and faster too. Please could you listen on my latest LoadRunner videos to comment on my speech? The link is kzbin.info/www/bejne/hmXTYmeQd72dfas

[@dineshmulage7171]

I have same question like how this value of 1.2 value you came up with ..? 20% extra per requirements mean .2 more but for 20% ur telling 1.2 hrs . So , in that case , each requirement takes .5hr mins to test and adding .2hr extra to .5 hrs , So its .7hrs . so it comes to 42 mins for each of the requirements including the explorative test . Can you please let me know if this correct understanding of mine .? . Can you please elobrate on this 1.2 value u came up and my above undertanding is correct thanks in advance .

[@QA1]

In my Test Estimation example, I estimated 0.5 hour per requirement. Then, added 20% for negative and exploratory testing. That is 0.6 hour per requirement. I did not use any hour to minute calculation. This factor of 20% is a guess. It should be validated from actual observations in existing project or other similar projects. If you think that 20% is high, you may want to use 10% extra time for negative and exploratory testing but definitely estimate time for this task. Finally, could you let me know at what timestamp did you hear "1.2 hrs"?

[@LayanSooriyaarachchi]

nice explanation... !!!

[@QA1]

@Layan Sooriyaarachchi, thank you for your comment.

[@sunitha6330]

Is test estimation done by the testing lead/manager for the project or is it to be done by the every individual tester for his/her part of the testing job?

[@QA1]

Exactly how is it done may vary from project to project. Yes, it is possible for individual testers to estimate their tasks. Then, the Test Lead includes their estimates in the overall test estimation. Alternately, the Test Lead may do the entire estimate him/her self. In order to get a realistic estimate, a person skilled in a task should estimate that task.

[@sunitha6330]

ok. thanks.

[@PradeepChauhan17]

The T9 value is in days and all other entities are in hours. Does it make any difference in estimates ?

[@QA1]

@Prads - Good observation. I have used T9 as Testing Days but you could use Testing Hours instead.

[@narottamsaini6951]

HI,, can you please explain Test case point (TCP) and Function case point (FCP) estimation technique.

[@tahiraaaasif8602]

. Could please guide me about QA testing and Test case development time during SDLC?

[@QA1]

Test case development and QA testing depends on the SDLC type. For example in Agile, test case development is needed in every iteration. Please view my Test Strategy video kzbin.info/www/bejne/rJ6YnHqva7qFoK8 at the following timestamps: 11:24 : Test Case Development, 12:53 : QA Testing

[@abdulvaheethmahabubjhon8451]

Super effort, Any link to download this

[@DS-rv2mf]

Is "1.2" for negative & exploratory testing a static value? can someone explain how we get that value ?

[@ManikandanKarunanithyQA]

Really Thank you very much for the amazing explanation of each clauses. One small request can you send me the Estimation excel to my email.

[@QA1]

+Manikandan Karunanithy Sure, please send your email address to plus.google.com/+InderPSingh

[@ravikumar-lk5we]

Sir, who performs this estimation,,whether seniour tester or the testers who do testing

[@QA1]

The person who does the test estimation should be the one who is proficient in testing and the system requirements. It can be the tester role, senior tester role or the test lead role.

[@sam-pm1yn]

Very good video, may I know where can I get the WBS templet you used please?

[@QA1]

sam Thank you for yoru comment. My WBS template is in the Microsoft Excel format. I have pasted it as a CSV below. You can save it as a .CSV file and open in Microsoft Excel.Task,Usage notes,Cumulative Effort Estimate(forumula),Cumulative Effort Estimate(hours)QA environment or test environment preparation,"Estimate this based on hardware installation, software installation and deployment of builds as T1, say 2 hours",T1,2Testing of n requirements,"Estimate testing time per requirement, T2, based on the detail of requirements e.g. T2 can be 0.5 if requirements are detailed up to 4 if the requirements are high level. Say 100 requirements and each testing time as 0.5 hour",T1 + T2 * n,52Negative and exploratory testing,"Use 20% extra testing time per requirement, to cover the paths other than the ?happy path?, and exceptional and invalid test data inputs.",T1 + T2 * n * 1.2,62Re-testing due to requirement correction or changes,"Estimate factor T3, based on requirement correctness and stability e.g. T3 can be 0.1 if requirements are well put and stable or 0.5 if requirements have multiple issues or are very dynamic. Let us use T3 as 0.2.",T1 + T2 * n * 1.4,72Logging defects and re-testing fixes,"Estimate the number of defects as T4. Estimate time to log defect, say 0.25 and time to re-test a fix, say 0.25. Say 10 defects",T1 + T2 * n * 1.4 + T4 * 0.25 + T4 * 0.25,77Regression testing,"Estimate this effort based on the impact of requirements implemented, defects and depth needed as T5, say 10 hours",T1 + T2 * n * 1.4 + T4 * 0.5 + T5,87Reserve,"Having this reserve helps to provide time to complete unforeseen tasks. Estimate the reserve as T6 between 5 and 10% of overall effort, say 10%",(T1 + T2 * n * 1.4 + T4 * 0.5 + T5) * (1 + T6),96Communication,Estimate the daily effort in hours on meetings and reporting as T7 say 0.5. Multiply it by team members T8 say 2 and number of testing days T9 say 6,(T1 + T2 * n * 1.4 + T4* 0.5 + T5) * (1 + T6) + T7 * T8 *T9,102

[@QA1]

***** The data is in my previous comment. It starts with "Task,Usage notes,Cumulative Effort Estimate(forumula),Cumulative Effort Estimate(hours)".

[@QA1]

***** Sorry to note that you are not sure how to save it as a .csv file. I will put the data again in my next comment below. Select all this data and copy by Ctrl+C. Then open Notepad. Paste the data by Ctrl+V. Then in Notepad, use Save As to save the file as Estimate.csv. Save As type dropdown should have All files value selected.Once the file is saved, in Windows, right-click the file and open in Microsoft Excel. Hope this works for you.

[@QA1]

Software and Testing TrainingTask,Usage notes,Cumulative Effort Estimate(forumula),Cumulative Effort Estimate(hours)QA environment or test environment preparation,"Estimate this based on hardware installation, software installation and deployment of builds as T1, say 2 hours",T1,2Testing of n requirements,"Estimate testing time per requirement, T2, based on the detail of requirements e.g. T2 can be 0.5 if requirements are detailed up to 4 if the requirements are high level. Say 100 requirements and each testing time as 0.5 hour",T1 + T2 * n,52Negative and exploratory testing,"Use 20% extra testing time per requirement, to cover the paths other than the ?happy path?, and exceptional and invalid test data inputs.",T1 + T2 * n * 1.2,62Re-testing due to requirement correction or changes,"Estimate factor T3, based on requirement correctness and stability e.g. T3 can be 0.1 if requirements are well put and stable or 0.5 if requirements have multiple issues or are very dynamic. Let us use T3 as 0.2.",T1 + T2 * n * 1.4,72Logging defects and re-testing fixes,"Estimate the number of defects as T4. Estimate time to log defect, say 0.25 and time to re-test a fix, say 0.25. Say 10 defects",T1 + T2 * n * 1.4 + T4 * 0.25 + T4 * 0.25,77Regression testing,"Estimate this effort based on the impact of requirements implemented, defects and depth needed as T5, say 10 hours",T1 + T2 * n * 1.4 + T4 * 0.5 + T5,87Reserve,"Having this reserve helps to provide time to complete unforeseen tasks. Estimate the reserve as T6 between 5 and 10% of overall effort, say 10%",(T1 + T2 * n * 1.4 + T4 * 0.5 + T5) * (1 + T6),96Communication,Estimate the daily effort in hours on meetings and reporting as T7 say 0.5. Multiply it by team members T8 say 2 and number of testing days T9 say 6,(T1 + T2 * n * 1.4 + T4* 0.5 + T5) * (1 + T6) + T7 * T8 *T9,102

[@QA1]

It is possible that the file is saved with a filename like Estimate.csv.txt. Right click on the file and click Properties. There you can remove the .txt at the end of the filename and then click the OK button. This should do it.

[@ravikumar-lk5we]

Sir, whet is the type of question i can expect from test estimation....plzz help

[@QA1]

Ten estimation questions and answers are given in this video itself. They start from approximately 15:00 into the video. Thank you.

[@ashibhargava]

Super effort, Any link to download this?

[@QA1]

Thank you 🙏 You can message me on LinkedIn at www.linkedin.com/in/inderpsingh/

[@ritu7180]

Do you have a Document of test estimation.

[@QA1]

ritika ritu No. In order not to burn time, it is great if you can refer the WBS of a similar project. Then, brainstorm to list all the planned activities of your unique project. Next, estimate the effort of each planned activity in your WBS.

[@Just_enjoy00]

From where u got 1.2 in 3rd step

[@QA1]

The 3rd task is Negative and Exploratory Testing. Adding 20 percent (i.e. 0.2 times) extra testing time per requirement gives T2*n*1.2. In other words, whatever time is estimated for testing one requirement, I estimated that it will take 20 percent extra time to additionally do negative and exploratory testing on that requirement. You may estimate this factor differently, say 0.1 for a rigid UI (e.g. a wizard style interface) or 0.3 for a flexible UI (e.g. a tool box based interface). Hope it is clearer!

[@PradeepChauhan17]

you have not accounted for the test cycles involved

[@QA1]

Prads - Ideally, there should be just one test cycle. But practically, there are 1) requirement clarifications/ changes 2) bug fixes that need re-testing and 3) regression testing. I have explained it from 10:15