A debugger value edit temporarily changes the current run. Use it to explore a soccer decision without confusing the experiment with a source-code repair.
A simple turn-limit check is enough; this page does not require loops.
Read the example once before trying to explain every line. Then use the short explanations below to connect each part of the code with the soccer task.
int numberOfTurns = 2;
string instruction = "Wait";
if (numberOfTurns < 3)
{
instruction = "Take a turn";
}Read the table one row at a time. Check when each value is observed: a value before a statement may differ from the value after that statement runs. Cover the result column and predict an answer before checking it.
| Experiment | Value when condition executes | Expected instruction |
|---|---|---|
| Fresh run | 2 | Take a turn |
| Edit before condition | 3 | Wait |
| Edit before condition | 0 | Take a turn |
Use the diagram to follow the same soccer example in a different form. Start at the beginning and follow one execution at a time. Compare the labeled actions with the source code; do not assume every action in the picture runs.
Write your prediction and a short reason first. If you test the change, compare the observed values with that prediction. When they differ, find the first statement or decision where your explanation stops matching the code.