IF/ELSE, FOR, WHILE, TRY/EXCEPT, BREAK, CONTINUE, and Control Flow: Configuration, Design Patterns, and Trade-Offs

1. Design principle: control flow should clarify intent, not merely reduce lines

Native syntax is concise, but fewer lines are not automatically more maintainable. The key question is whether a reviewer can predict which branch runs, what failure is recoverable, how long repetition can last, and which state is mutated. If those answers require mentally executing a mini-program, the abstraction is too low for the test layer.

2. Native syntax versus helper keyword versus Python

3. FOR versus data templates

A FOR loop means one test/task performs repeated steps. If the third iteration fails, the overall item fails as one result and preceding iterations are evidence inside that same result. A test template (Chapter 11) generates semantically separate data-driven cases or iterations according to template rules. Choose based on result identity, not just source compactness.

4. WHILE versus a bounded polling keyword

WHILE is useful when each iteration has meaningful orchestration. For a common readiness condition, a named polling keyword is often clearer because it owns the deadline, interval, evidence, and failure message. Avoid using an arbitrary Robot loop to imitate a domain library’s condition-specific wait when that library can observe readiness directly.

Wait For Synthetic State
    [Arguments]    ${expected}    ${max_attempts}=6
    VAR    ${attempt}    ${0}
    WHILE    ${attempt} < ${max_attempts}    limit=${max_attempts}
        ${attempt}=    Evaluate    $attempt + 1
        ${actual}=     Read Synthetic State    ${attempt}
        Log    attempt=${attempt}; actual=${actual}
        IF    $actual == $expected
            RETURN    ${actual}
        END
    END
    Fail    State did not become '${expected}' in ${max_attempts} attempts

5. Match errors as narrowly as the contract allows

6. ${var} replacement versus $var access

7. Inline IF is for one-statement branches, not compressed programs

Inline IF can make small choices readable, especially with RETURN, BREAK, or CONTINUE. Once several ELSE IF branches or long arguments appear, use normal block syntax. Compression increases review cost and makes failure traces harder to scan.

IF    $item is None    CONTINUE
IF    $state == "ready"    RETURN    ${state}

8. Legacy-compatible BuiltIn controls are not the modern design default

Run Keyword If remains supported, but the User Guide generally recommends native IF/ELSE. Likewise Exit For Loop and Continue For Loop still work for compatibility, but native BREAK/CONTINUE are recommended and the older loop-control keywords are planned for eventual deprecation/removal. Do not introduce the wrapper style into a new 7.4.2 course unless dynamic keyword dispatch is the real requirement.

9. Runtime and output trade-offs

Large loops expand output.xml and log.html. Repeated polling also consumes external capacity. Optimize only after measurement: count iterations, measure elapsed time, identify external latency, and preserve enough loop detail for diagnosis. --removekeywords/--flattenkeywords can reduce result size later, but they should not be used to hide evidence while designing a flaky loop.

10. Parallelism and shared state

Control flow does not create isolation. A FOR loop that mutates one shared file or account is still unsafe if multiple tests/workers use the same resource later with Pabot. Use unique identities and narrow state ownership from earlier chapters; a branch or loop only chooses operations on that state.

11. Worked decision scenario

12. Knowledge check

13. Summary and next step

Control-flow design is a placement decision. Use native syntax for small readable orchestration, user keywords for reusable bounded contracts, templates for data-driven result identity, and Python for algorithmic complexity. Lesson 4 applies these choices to realistic failure modes and diagnosis.

Further reading

• Robot Framework 7.4.2 User Guide — control structures — FOR, WHILE, BREAK/CONTINUE, IF/ELSE, TRY/EXCEPT, and readability guidance.
• Robot Framework 7.4.2 User Guide — WHILE loops — expression evaluation, limits, on_limit, and output-size considerations.
• Robot Framework 7.4.2 User Guide — TRY/EXCEPT — exact/pattern matching, AS, ELSE, FINALLY, and uncatchable failures.
• Robot Framework 7.4.2 User Guide — evaluating expressions — ${var} replacement versus $var access and evaluation namespace behavior.
• Robot Framework 7.4.2 BuiltIn — legacy-compatible conditional/loop-control helpers and native-syntax recommendations.
• Robot Framework project site — current stable release stream.