Enforced Rules
Enforced Rules are mandatory standards and platform behaviors that must be followed during various stages of test authoring and execution. These rules are either built directly into the Sofy platform or enforced by its design.
- Acquire Device -- Devices can only be acquired based on the active device limit plan. A device must be in an "Available" state to be acquired. Offline or already-in-use devices cannot be launched or selected.
- Device Session: Users should be aware of the session time limit and extend it if needed to avoid disruptions during testing. It is also recommended to break long recordings into smaller segments to allow the device to cool down, as extended usage without breaks may impact performance.
- Starting Recording -- Recording can only begin after successfully acquiring a device. Manual step editing during an active recording session is not allowed unless the edit icon is clicked for a recorded step. The session cannot be saved if recording ends midway or the tab is accidentally closed.
- Recording Steps -- Only supported actions (e.g., long click, type, scroll, mock location, API steps, switch apps, etc.) are captured. Actions like "Scroll Until Visible" and "Time Delay" must be explicitly triggered by the user.
- Step Categories -- At least one step is required for a test to be marked as "Ready." Steps such as conditionals, delays, and scrolls must follow a logical and executable test flow.
- Saving Test -- Saving is restricted until the test includes a valid minimum structure (device selection and valid steps). A test cannot be saved as "Ready" unless all required validations are satisfied.
- Test Case Failed: Use the "Open to Compare with Recording" feature to identify the exact step where the test case failed. This helps in pinpointing the failure and understanding the deviation from expected behavior.
- App Crash: Review the crash logs to identify the root cause of the issue and determine the reason behind the application failure.
- Use of Test Case Variables: Test case variables are used to store and manage test data, allowing for more flexible, reusable, and maintainable test scenarios.
