Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

ISTQB-CTFL Exam - Topic 5 Question 39 Discussion

Posted by Annelle on Jan 27, 2025 at 03:29 AM

Which of the following best describes the way in which statement coverage is measured?

Suggested Answer: C

Statement coverage is a metric used in white-box testing that measures the percentage of executable statements in the code that have been executed by the test cases. It is calculated as the number of statements executed by the tests divided by the total number of executable statements in the code, providing an indication of how much of the code has been tested.


Get Premium ISTQB-CTFL Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
34 comments · newest first
GL
Glory 10 months ago
Definitely option C, that's how I've always understood it.
CA
Carry 11 months ago
Wait, is it really just about lines of code? Sounds too simple.
DE
Delfina 11 months ago
No way, B can't be true. We can measure it!
JO
Jodi 11 months ago
I think it's option C, that makes the most sense.
ET
Ettie 11 months ago
Statement coverage is all about executed statements, right?
SH
Shawnna 12 months ago
I vaguely recall that statement coverage is related to lines of code, but I can't remember if it's about executable statements or just any line of code.
DE
Deeanna 12 months ago
I feel like I might be mixing up statement coverage with decision coverage. I need to double-check what exactly each one measures.
PE
Penney 12 months ago
I remember practicing a question similar to this, and I think it was definitely about the number of statements executed. So, I lean towards C.
SH
Shawnna 1 year ago
I think statement coverage is about measuring how many statements are executed, but I'm not sure if it's option C or D.
SA
Santos 1 year ago
Okay, I think I've got this. Statement coverage is about measuring how much of the actual code is being executed by the tests, not just the lines of code. So it's the number of statements executed divided by the total number of executable statements, which matches option C. I'm feeling good about that one.
SU
Susana 1 year ago
I'm not too confident on this one. I know statement coverage is related to the code, but I can't quite recall the exact definition. I'll have to review my notes and try to eliminate the options that don't sound right. Hopefully I can narrow it down and make an educated guess.
JI
Jin 1 year ago
Ah, I remember learning about this in class. Statement coverage is not about lines of code, but rather the number of executable statements that are covered by the tests. So option C is the right answer - it's the number of statements executed divided by the total number of executable statements.
KE
Kenda 1 year ago
Hmm, I'm a bit confused on this one. I know statement coverage has something to do with the number of lines of code executed, but I'm not sure if it's measured as the number of lines executed divided by the total lines, or something else. I'll have to think this through carefully.
AP
Apolonia 1 year ago
I'm pretty sure statement coverage is measured by the number of statements executed by the tests, divided by the total number of executable statements in the code. Option C seems to be the correct answer.
JA
Jamal 2 years ago
Statement coverage? More like 'statement hovercraft' am I right? *crickets*
LE
Levi 2 years ago
I heard the test organizers are using a new statement coverage metric - the number of times the tester says 'wait, what?' during the exam.
GW
Gwenn 2 years ago
Option A sounds like it's measuring decision coverage, not statement coverage. I'll go with C as the best answer here.
NU
Nu 2 years ago
B? Are you kidding me? Of course it's possible to measure statement coverage. This question is a no-brainer!
LA
Latrice 2 years ago
↳ replying to Nu
C) Measured as the number of statements executed by the tests, divided by the total number of executable statements in the code.
JA
Jamal 2 years ago
↳ replying to Nu
A) Measured as the number of decision outcomes executed by the tests, divided by the total number of decision outcomes in the test object.
AV
Avery 2 years ago
I agree with Tonja, option A seems like the most logical way to measure statement coverage.
TO
Tonja 2 years ago
I think option A is correct, as it makes sense to measure based on decision outcomes.
LO
Lorrine 2 years ago
Option D is clearly wrong. Line of code is not the same as a statement, so that's not a valid way to measure statement coverage.
MA
Maricela 2 years ago
↳ replying to Lorrine
A) Measured as the number of decision outcomes executed by the tests, divided by the total number of decision outcomes in the test object.
MO
Moon 2 years ago
↳ replying to Lorrine
I agree, option D is definitely incorrect. It's important to measure statement coverage accurately.
SH
Sheron 2 years ago
↳ replying to Lorrine
C) Measured as the number of statements executed by the tests, divided by the total number of executable statements in the code.
CA
Carmelina 2 years ago
↳ replying to Lorrine
A) Measured as the number of decision outcomes executed by the tests, divided by the total number of decision outcomes in the test object.
SI
Simona 2 years ago
I think option C is the correct answer. It makes the most sense to measure statement coverage by the number of statements executed versus the total number of executable statements.
GE
Geraldine 2 years ago
↳ replying to Simona
I'm not sure, but I think option C is the most accurate answer.
TA
Tasia 2 years ago
↳ replying to Simona
I believe option D could also be a possible method of measuring statement coverage.
DE
Deeanna 2 years ago
↳ replying to Simona
I think option A might also be a valid way to measure statement coverage.
AR
Arthur 2 years ago
↳ replying to Simona
I agree, option C seems like the most logical choice.
LE
Lettie 2 years ago
I disagree, I believe it's measured by the number of statements executed.
TU
Tuyet 2 years ago
I think statement coverage is measured by the number of decision outcomes executed.
0/2000 characters

Save Cancel