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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

iSQI Exam CTAL-ATT Topic 9 Question 45 Discussion

Actual exam question for iSQI's CTAL-ATT exam
Question #: 45
Topic #: 9
[All CTAL-ATT Questions]

When test cases are re-run after refactoring, what should always be verified?

Show Suggested Answer Hide Answer
Suggested Answer: D

by Shawnna at Sep 19, 2024, 12:14 AM

Limited Time Offer

25%

Off

Get Premium CTAL-ATT Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Sharmaine
2 months ago
I'm with Jarod on this one. Refactoring is all about improving the code under the hood, not changing the way it behaves. C is the answer.
upvoted 0 times
...
Jestine
2 months ago
C is the way to go. If the refactored code doesn't give the same results, then you've got a bigger problem on your hands!
upvoted 0 times
Glendora
3 days ago
D) That tests that have now been made redundant are removed from the test set
upvoted 0 times
...
Melodie
15 days ago
C) That they provide the same results as before
upvoted 0 times
...
Denny
29 days ago
A) That the branch coverage is the same or increased
upvoted 0 times
...
...
Delfina
2 months ago
A seems like a strange choice. Branch coverage is important, but it's not the first thing I'd check after a refactoring. I'm sticking with C.
upvoted 0 times
Freeman
28 days ago
I see your point, but I still think C is the most crucial to verify after refactoring.
upvoted 0 times
...
Marge
29 days ago
I think A is also important to ensure we are not missing any critical paths in the code.
upvoted 0 times
...
Cletus
2 months ago
I agree, C is the safest choice. We need to make sure the results are consistent.
upvoted 0 times
...
...
Shenika
2 months ago
B is a bit of a stretch. Better logging is a nice-to-have, but it's not the priJarod concern when refactoring. I'd go with C.
upvoted 0 times
Josphine
29 days ago
D is also crucial. We should remove any redundant tests to keep our test set efficient.
upvoted 0 times
...
Whitley
2 months ago
I think A is also important. We need to ensure that the branch coverage is maintained or improved.
upvoted 0 times
...
Darrel
2 months ago
I agree, C is the most important. We need to make sure the results are the same after refactoring.
upvoted 0 times
...
...
Justine
2 months ago
D makes sense too. If you've refactored the code, some tests might have become redundant and should be removed to keep the test suite lean and efficient.
upvoted 0 times
Sherly
9 days ago
D) That tests that have now been made redundant are removed from the test set
upvoted 0 times
...
Charlene
25 days ago
C) That they provide the same results as before
upvoted 0 times
...
Ellen
1 months ago
A) That the branch coverage is the same or increased
upvoted 0 times
...
...
Jarod
2 months ago
I think C is the correct answer. The whole point of refactoring is to improve the code without changing its functionality, so the test results should be the same.
upvoted 0 times
...
Ruthann
3 months ago
But shouldn't we also check if any tests have become redundant and remove them from the test set?
upvoted 0 times
...
German
3 months ago
I agree with Jamal. It's important to make sure the refactored code still produces the same results.
upvoted 0 times
...
Jamal
3 months ago
I think we should always verify that the test cases provide the same results as before.
upvoted 0 times
...

Save Cancel