Tips & Tricks
RobotCode analyzes your Robot Framework code without running it. These pages explain how to structure resource files and variables so that the analysis can follow them, and why some findings appear although the tests run.
Avoiding a Global Resource FileWhy one catch-all resource file causes circular imports, ambiguous keywords and slow analysis, how to modularize it, and how to suppress the warnings.
Why is my variable shown as "not found"?Why RobotCode's static analysis flags VariableNotFound for variables that work at runtime, and how Variables sections, defaults and RETURN avoid it.
Released under the Apache-2.0. Copyright © 2022-present Daniel Biehl