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

AThe quality of the development estimate may be poor.

BIn general bottom-up estimation is always better than top-down estimation.

CThe percentage based technique only applies to the V life cycle model.

DUsing the same percentage every time does not address the level of risk of the application to be tested.

EThe 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.

FIt builds on large set of historical data

GThe result is almost always a too low estimate for the required test effort

Show Suggested 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:

Submit Cancel

Marva

23 days 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

2 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

7 days ago

A) The quality of the development estimate may be poor.

upvoted 0 times

...

Nenita

26 days 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

29 days 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

Mattie

4 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

6 days ago

A) The quality of the development estimate may be poor.

upvoted 0 times

...

Na

1 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

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