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 Exam CT-TAE Topic 1 Question 28 Discussion

Actual exam question for ISTQB's CT-TAE exam
Question #: 28
Topic #: 1
[All CT-TAE Questions]

Which of the following metrics could suggest, under certain condition that an automated regression test suite has NOT been updated for new functionalities added to the SUT?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Shawnee
3 months ago
Choosing D, just because I like the idea of a high ratio of commands to executable statements. Sounds like a fun problem to solve!
upvoted 0 times
Devon
1 months ago
User3: I'm going with C, defect density in automation code seems like a good metric to consider.
upvoted 0 times
...
Mitzie
1 months ago
User2: I agree with User1, code coverage is a good indicator of test suite updates.
upvoted 0 times
...
Junita
2 months ago
User1: I think B is the answer, code coverage is important for regression testing.
upvoted 0 times
...
...
Mari
3 months ago
I'm going to have to go with B. High code coverage is a good sign that the regression suite is up-to-date.
upvoted 0 times
Elroy
2 months ago
I'm not sure about that, I believe the ratio of comments to executable statements is a better metric to consider.
upvoted 0 times
...
Marjory
2 months ago
I think the defect density in the automation code could also suggest if the suite has been updated.
upvoted 0 times
...
Leanora
2 months ago
I agree with you, high code coverage is definitely a good indicator.
upvoted 0 times
...
...
Junita
3 months ago
Hmm, I'm not sure about this one. I was thinking C, but I'm open to other opinions. Anyone else have thoughts?
upvoted 0 times
Ilene
1 months ago
D) The ratio of commands to executable statements in the automation code of the regression test suite
upvoted 0 times
...
Sylvia
1 months ago
C) The defect density in the automation code of the regression test suite.
upvoted 0 times
...
Billye
2 months ago
B) The SUT code coverage provided by the execution of the regression test suite.
upvoted 0 times
...
Theola
2 months ago
A) The ratio of comments to executable statements in the SUT code.
upvoted 0 times
...
...
Brent
3 months ago
I'm going with D. The ratio of commands to executable statements in the automation code could suggest the tests haven't been updated.
upvoted 0 times
Rolande
2 months ago
I see your point, but I still believe D is more accurate. The ratio of commands to executable statements directly reflects the test suite's update status.
upvoted 0 times
...
Rosendo
3 months ago
I think B is a better indicator. Code coverage from the regression tests can show if new functionalities have been tested.
upvoted 0 times
...
...
Kristeen
3 months ago
But what about option B) The SUT code coverage provided by the execution of the regression test suite? Wouldn't that also indicate if the test suite has not been updated?
upvoted 0 times
...
Ivory
3 months ago
I think B is the correct answer. If the regression test suite doesn't cover new functionalities, the code coverage will be low.
upvoted 0 times
...
Anglea
3 months ago
I agree with Myra. If the automation code has a high defect density, it could suggest that the test suite has not been updated for new functionalities.
upvoted 0 times
...
Myra
4 months ago
I think the answer is C) The defect density in the automation code of the regression test suite.
upvoted 0 times
...

Save Cancel