MENU
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
Suggested Answer: C
Get Premium CTFL Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
39 comments · newest first
CA
Carmela
11 months ago
Maturity of the organization really does play a big role in testing effort.
YU
Yuette
11 months ago
Using the same percentage every time is a bad idea, for sure.
ME
Melynda
12 months ago
Wait, does that mean we can't trust the dev estimates at all?
KA
Karl
12 months ago
Totally agree, it's risky to rely on just percentages!
LA
Laine
1 year ago
The quality of the development estimate may be poor.
LO
Louisa
1 year ago
I feel like the percentage method might lead to underestimating the testing effort, especially if the project is complex.
TH
Thurman
1 year 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.
MA
Major
1 year ago
I'm not entirely sure, but I think using a fixed percentage doesn't consider the unique risks of each project, right?
PH
Phyliss
1 year ago
I remember discussing how the quality of the development estimate can really impact the testing effort, so that might be one reason.
ED
Eden
1 year 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.
ME
Melissa
1 year 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.
WI
William
1 year 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.
SK
Skye
1 year 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.
XE
Xenia
1 year ago
I'm pretty confident about this one. I think the correct answers are B and D.
IR
Irma
1 year 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.
LO
Lorean
1 year 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.
MA
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.
PE
Pete
1 year ago
G) The result is almost always a too low estimate for the required test effort
VE
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.
JE
Jerry
1 year ago
A) The quality of the development estimate may be poor.
NE
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.
OM
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.
LA
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.
MA
Mattie
1 year ago
D) Using the same percentage every time does not address the level of risk of the application to be tested.
NE
Nenita
1 year ago
A) The quality of the development estimate may be poor.
NA
Na
2 years 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.
SE
Selma
1 year ago
G) The result is almost always a too low estimate for the required test effort
SA
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.
ST
Stefany
1 year ago
A) The quality of the development estimate may be poor.
JA
Jamal
2 years 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.
PA
Paola
1 year ago
G) The result is almost always a too low estimate for the required test effort
JA
Janey
1 year ago
D) Using the same percentage every time does not address the level of risk of the application to be tested.
MA
Marget
1 year ago
E) The maturity of the organization also influences the effort needed for testing.
AD
Adelle
1 year ago
E) The maturity of the organization also influences the effort needed for testing.
CO
Cordie
2 years ago
A) The quality of the development estimate may be poor.
YV
Yvonne
2 years ago
A) The quality of the development estimate may be poor.
LA
Laticia
2 years ago
I also believe that the result is almost always a too low estimate for the required test effort.
ID
Idella
2 years ago
I agree with Ashley. Using the same percentage every time does not address the level of risk of the application to be tested.
AS
Ashley
2 years ago
I think it's not a good idea because the quality of the development estimate may be poor.