Challenge 1: Choosing the Right Stepping Action — Solution Walkthrough

The answer:

Step Over.

Why, per this chapter's own definitions:

Step Over runs the current line's function call to completion without
descending into its own internals — exactly what's needed here, since
the helper function is already trusted to be working correctly and
there's no reason to spend time watching its own line-by-line
execution. Execution continues past the call, landing on the next
line in the current function, having still fully executed the helper
in the background.

Why the other two options don't fit:

Step Into would descend into the helper function's own code line by
line, which is unnecessary time spent watching internals you already
trust. Step Out would finish the entire current function (not just
the one helper call) and return to whatever called it — going too far
past the point of interest, skipping over other code in the current
function that may still need to be stepped through.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that the three stepping actions from this
chapter are understood well enough to pick the correct one for a
specific, realistic debugging situation, not just to recall their
definitions in isolation.