Best Practices for System Commands
System Commands allow Drizz to interact directly with the device and application lifecycle beyond standard UI-based actions. Because they operate at a lower system level launching apps, killing processes, clearing data, or managing multi-app workflows, they must be used carefully and with precise syntax. This section outlines best practices to ensure stability, prevent unintended resets, and maintain predictable test execution when working with powerful commands.
Recommended Best Practices for Writing System Commands:
Use system commands only when UI-based commands are insufficient They operate outside normal UI interactions.
System command syntax must be exact Any deviation results in failure.
Avoid chaining multiple system actions in one step Each must be executed independently.
Use CLEAR_APP cautiously It resets the entire app state and may invalidate prior steps.
Prefer OPEN_APP for multi-app workflows Helps test external handoffs (payments, maps, verification apps).
Always validate after a system command e.g., after KILL_APP, validate the home/login screen.
Last updated
Was this helpful?