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

- Free Preparation Discussions

ASTQB Exam CTFL 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

Contribute your Thoughts:

Marva
1 months 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
Velda
10 days 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
16 days ago
A) The quality of the development estimate may be poor.
upvoted 0 times
...
...
Nenita
1 months 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 months 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
6 days 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
12 days 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
15 days ago
A) The quality of the development estimate may be poor.
upvoted 0 times
...
...
Na
2 months 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 months ago
G) The result is almost always a too low estimate for the required test effort
upvoted 0 times
...
Sabra
1 months 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 months ago
A) The quality of the development estimate may be poor.
upvoted 0 times
...
...
Jamal
2 months 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
9 days ago
G) The result is almost always a too low estimate for the required test effort
upvoted 0 times
...
Janey
24 days 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
29 days ago
E) The maturity of the organization also influences the effort needed for testing.
upvoted 0 times
...
Adelle
1 months ago
E) The maturity of the organization also influences the effort needed for testing.
upvoted 0 times
...
Cordie
2 months ago
A) The quality of the development estimate may be poor.
upvoted 0 times
...
Yvonne
2 months ago
A) The quality of the development estimate may be poor.
upvoted 0 times
...
...
Laticia
2 months ago
I also believe that the result is almost always a too low estimate for the required test effort.
upvoted 0 times
...
Idella
2 months 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
2 months ago
I think it's not a good idea because the quality of the development estimate may be poor.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77