U.S. Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

ASTQB CTFL Exam - Topic 3 Question 63 Discussion

In general, why is it NOT a good idea to estimate the testing effort based only on a percentage of development effort? Identify THREE valid reasons. 1 credit
C) The percentage based technique only applies to the V life cycle model.
A) The quality of the development estimate may be poor.
B) In general bottom-up estimation is always better than top-down estimation.
D) Using the same percentage every time does not address the level of risk of the application to be tested.
E) The maturity of the organization, e.g. the quality of the test basis, quality of development testing, configuration management, availability of test tools, also influence the effort needed for testing.
F) It builds on large set of historical data
G) The result is almost always a too low estimate for the required test effort

ASTQB CTFL Exam - Topic 3 Question 63 Discussion

Actual exam question for ASTQB's CTFL exam
Question #: 63
Topic #: 3
[All CTFL Questions]

In general, why is it NOT a good idea to estimate the testing effort based only on a percentage of development effort? Identify THREE valid reasons. 1 credit

Show Suggested Answer Hide Answer
Suggested Answer: C

by Aleta at Jun 03, 2024, 07:01 AM

Limited Time Offer

25%

Off

Get Premium CTFL Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Carmela
7 months ago
Maturity of the organization really does play a big role in testing effort.
upvoted 0 times
...
Yuette
7 months ago
Using the same percentage every time is a bad idea, for sure.
upvoted 0 times
...
Melynda
7 months ago
Wait, does that mean we can't trust the dev estimates at all?
upvoted 0 times
...
Karl
7 months ago
Totally agree, it's risky to rely on just percentages!
upvoted 0 times
...
Laine
7 months ago
The quality of the development estimate may be poor.
upvoted 0 times
...
Louisa
8 months ago
I feel like the percentage method might lead to underestimating the testing effort, especially if the project is complex.
upvoted 0 times
...
Thurman
8 months ago
I practiced a similar question, and I think the maturity of the organization plays a big role in how much effort is actually needed for testing.
upvoted 0 times
...
Major
8 months ago
I'm not entirely sure, but I think using a fixed percentage doesn't consider the unique risks of each project, right?
upvoted 0 times
...
Phyliss
8 months ago
I remember discussing how the quality of the development estimate can really impact the testing effort, so that might be one reason.
upvoted 0 times
...
Eden
8 months ago
Ah, this is the kind of question I was hoping to see. I've learned that estimating testing effort based on a percentage of development effort can be risky, and I'm confident I can identify three valid reasons why. I'll need to be clear and concise in my response.
upvoted 0 times
...
Melissa
8 months ago
Hmm, this is an interesting question. I know that using a percentage-based approach can be problematic, but I'll need to really analyze the options and think about the specific reasons why it's not recommended. I want to make sure I provide a thorough and well-reasoned response.
upvoted 0 times
...
William
8 months ago
This question seems straightforward, but I want to make sure I understand the reasoning behind it. I'll need to think carefully about the potential issues with using a percentage-based approach for estimating testing effort.
upvoted 0 times
...
Skye
8 months ago
Okay, let me see if I can come up with three valid reasons why it's not a good idea to estimate testing effort based solely on a percentage of development effort. I'll need to consider factors like the quality of the development estimate, the life cycle model, and the overall maturity of the organization.
upvoted 0 times
...
Xenia
8 months ago
I'm pretty confident about this one. I think the correct answers are B and D.
upvoted 0 times
...
Irma
9 months ago
The key here is to focus on the specific metric that relates to free storage space for the DB Instance. I think the answer is B, FreeStorageSpace.
upvoted 0 times
...
Lorean
9 months ago
Okay, let's see. The question is asking about the best way to identify risk from a social engineering attack, but the answer choices seem to be focused on IoT device acquisition. I'm a bit confused.
upvoted 0 times
...
Marva
1 year ago
Bingo! The organization's maturity is crucial. If the test basis, dev testing, and tooling are all top-notch, the testing effort might be lower. But if it's a hot mess, you're in for a wild ride. Gotta account for that upfront.
upvoted 0 times
Pete
12 months ago
G) The result is almost always a too low estimate for the required test effort
upvoted 0 times
...
Velda
1 year ago
E) The maturity of the organization, e.g. the quality of the test basis, quality of development testing, configuration management, availability of test tools, also influence the effort needed for testing.
upvoted 0 times
...
Jerry
1 year ago
A) The quality of the development estimate may be poor.
upvoted 0 times
...
...
Nenita
1 year ago
Exactly, using a one-size-fits-all percentage doesn't cut it. The risk profile of the application is key. You can't just slap on a generic percentage and call it a day. Gotta dig deeper.
upvoted 0 times
...
Omer
1 year ago
Hah, the V-life cycle model? Really? That's so 1990s. No, this approach doesn't work for any modern software development methodology. We need to take a more holistic view of the risks and challenges.
upvoted 0 times
Lai
1 year ago
E) The maturity of the organization, e.g. the quality of the test basis, quality of development testing, configuration management, availability of test tools, also influence the effort needed for testing.
upvoted 0 times
...
Mattie
1 year ago
D) Using the same percentage every time does not address the level of risk of the application to be tested.
upvoted 0 times
...
Nenita
1 year ago
A) The quality of the development estimate may be poor.
upvoted 0 times
...
...
Na
1 year ago
Ah, the old 'bottom-up is always better' argument. But that's not always the case. The percentage-based technique can work in certain contexts, like the V-model. We need to consider the specific project and organization's maturity.
upvoted 0 times
Selma
1 year ago
G) The result is almost always a too low estimate for the required test effort
upvoted 0 times
...
Sabra
1 year ago
E) The maturity of the organization, e.g. the quality of the test basis, quality of development testing, configuration management, availability of test tools, also influence the effort needed for testing.
upvoted 0 times
...
Stefany
1 year ago
A) The quality of the development estimate may be poor.
upvoted 0 times
...
...
Jamal
1 year ago
Estimating testing effort solely based on development effort is a risky approach. The quality of the development estimate can be poor, and that would directly impact the testing estimate. Gotta look at more factors here.
upvoted 0 times
Paola
1 year ago
G) The result is almost always a too low estimate for the required test effort
upvoted 0 times
...
Janey
1 year ago
D) Using the same percentage every time does not address the level of risk of the application to be tested.
upvoted 0 times
...
Marget
1 year ago
E) The maturity of the organization also influences the effort needed for testing.
upvoted 0 times
...
Adelle
1 year ago
E) The maturity of the organization also influences the effort needed for testing.
upvoted 0 times
...
Cordie
1 year ago
A) The quality of the development estimate may be poor.
upvoted 0 times
...
Yvonne
1 year ago
A) The quality of the development estimate may be poor.
upvoted 0 times
...
...
Laticia
1 year ago
I also believe that the result is almost always a too low estimate for the required test effort.
upvoted 0 times
...
Idella
1 year ago
I agree with Ashley. Using the same percentage every time does not address the level of risk of the application to be tested.
upvoted 0 times
...
Ashley
1 year ago
I think it's not a good idea because the quality of the development estimate may be poor.
upvoted 0 times
...

Save Cancel