Question

question 5 of 10
a programmer is debugging an action - adventure game they have just created.
as they test the game, they make only the moves and decisions that players
of the game are most likely to make. is this a good strategy for debugging a
game? why or why not?

a. yes, because this is where players are most likely to notice errors

b. yes, because errors are most likely to be overlooked in obvious
places

c. no, because making expected moves is not likely to test the
games limits

d. no, because playing successfully is not part of the debugging
process

Explanation:

To determine the answer, we analyze each option:

• Option A: If the programmer only makes expected moves, they might miss errors that occur in less - common scenarios, so this is not a good reason for the strategy being good.
• Option B: Errors in obvious places (expected moves) are actually more likely to be found, not overlooked, so this is incorrect.
• Option C: Debugging should test the game's limits, edge cases, etc. If the programmer only makes expected moves, they won't test the game in situations where it might break (like unusual inputs or actions), so this strategy is bad for debugging.
• Option D: Playing successfully can be part of debugging to ensure the normal flow works, but the main issue with the strategy is not testing the limits, so this is not the correct reasoning.

Answer:

C. No, because making expected moves is not likely to test the game's limits