Project Management

Please login or join to subscribe to this thread

how to estimate the time ratio of unit testing in the development process?

linkedin twitter facebook   Testing/Test Management  
avatar
xia maocheng
In agile practice, we need a prototype to provide to customers, which helps to quickly meet their expectations and increase expected value. In the practical process, detection tools such as paid or open-source ones should be provided to improve the rapid feedback and quality evaluation of the project. Normally, we should first predict the core functions and estimate their proportion in the actual plan. When at the expected level, we should update the testing plan and cases,
Otherwise, we should adjust the schedule according to the actual development plan to ensure a steady increase in the progress coefficient.
But how to estimate the time ratio of unit testing in the development process?
Sort By:
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
It will fully depends on your defined process and the quality of your deliverables. A magic number that has been empirical proven in software engineering  is 40-20-40 where the last 40 is related to testing (all type of testing you will use).
...
1 reply by Sunil Chainani
Dec 27, 2024 12:50 AM
Sunil Chainani
...
What is the 40-20 in the 40-20-40 approach suggested?
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Xia -

This really depends on a number of factors including quality objectives, nature of the underlying code, its complexity, the tools used for developing & capturing the unit tests and the testing coverage.

In some cases it could be as much as or even more than the effort involved in writing the code, especially if the test case automation is challenging to use.

Kiron
avatar
Sunil Chainani Sr. Manger, PMO Process Improvement| Xylem Kenosha, Wi, United States
Dec 25, 2024 8:19 AM
Replying to Sergio Luis Conte
...
It will fully depends on your defined process and the quality of your deliverables. A magic number that has been empirical proven in software engineering  is 40-20-40 where the last 40 is related to testing (all type of testing you will use).
What is the 40-20 in the 40-20-40 approach suggested?
...
1 reply by Sergio Luis Conte
Dec 28, 2024 7:42 AM
Sergio Luis Conte
...
40% of the time is about all activities previous to construction.
20% of the time is about activities performing during construction.
40% of the time is about all the activities post construction.
The key is how to distribute the percentage because it will depends on lot of factors but mainly about the approach you are using.
From long, long time ago when organizations takes statistics about the cycle time this ratio persists.
avatar
Abolfazl Yousefi Darestani Manager, Quality and Continuous Improvement| Hörmann-TNR Industrial Doors Newmarket, Ontario, Canada
Depends of lots of factors. Experience and similar projects could be a good reference.
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
Dec 27, 2024 12:50 AM
Replying to Sunil Chainani
...
What is the 40-20 in the 40-20-40 approach suggested?
40% of the time is about all activities previous to construction.
20% of the time is about activities performing during construction.
40% of the time is about all the activities post construction.
The key is how to distribute the percentage because it will depends on lot of factors but mainly about the approach you are using.
From long, long time ago when organizations takes statistics about the cycle time this ratio persists.

Please login or join to reply

Content ID:
ADVERTISEMENTS

Wow! They've got the internet on computers now!

- Homer Simpson

ADVERTISEMENT

Sponsors







Vendor Events

See all Vendor Events

Newsletters

Jun 3: The Career Problem Facing New PMs
May 20: Your PM Career as a Project Life Cycle
May 13: The Big Lie After Layoffs

See all newsletters