Overview
Macros are reusable sequences of test steps that:- Reduce repetitive work
- Ensure consistency across tests
- Speed up test case creation
- Simplify maintenance
Accessing Macro Manager
From Remote Test Manager
- Open the Remote Test Manager
- Click the Settings (⚙️) button
- Select Macro Manager
From Mobile Test Designer
- In the step editor
- Click Insert Macro
- Browse and select macros
Interface Layout
Browsing Macros
Platform Filter
Filter macros by platform:- All: Show all macros
- Web: Web application macros
- iOS: iOS-specific macros
- Android: Android-specific macros
- Mobile: Both iOS and Android
- API: API testing macros
Search
- Enter search text in the search box
- Search matches:
- Macro name
- Macro description
- Click 🔍 or press Enter to search
Macro List
The list displays:Creating a Macro
Step 1: Click New Macro
Click the [+ New Macro] button.Step 2: Configure Macro
- Name: Enter a descriptive name
- Description: Explain what the macro does
- Platform: Select target platform(s)
Step 3: Define Steps
Add steps to the macro:- Click Add Step
- Configure step type (tap, swipe, input, etc.)
- Set step parameters
- Repeat for additional steps
Step 4: Save
Click Save to create the macro.Macro Step Types
Macros support the same step types as test cases:
See Step Types Reference for details.
Editing Macros
Modify Existing Macro
- Find the macro in the list
- Click the Edit button
- Make changes to name, description, or steps
- Click Save
Duplicate Macro
- Select the macro
- Click Duplicate
- Modify the copy as needed
- Save with a new name
Deleting Macros
Delete a Macro
- Select the macro
- Click Delete
- Confirm the deletion
Warning: Deleting a macro may affect test cases that use it. Review usage before deleting.
Using Macros in Test Cases
In Mobile Test Designer
- Open a test case in Mobile Test Designer
- Position cursor where you want to insert
- Click Insert Macro
- Select the macro
- Steps are added to your test case
Macro Expansion
When a macro is inserted:- All macro steps are copied to the test case
- Steps become part of the test case
- Changes to the macro don’t affect already-inserted steps
Best Practices
Naming Conventions
- Use descriptive names: “Login with Valid Credentials”
- Include platform if specific: “iOS Login Flow”
- Avoid abbreviations unless standard
When to Use Macros
- Login/Logout flows: Common across many tests
- Navigation sequences: Opening specific screens
- Data setup: Creating test data
- Verification patterns: Standard checks
Maintenance Tips
- Document macros with descriptions
- Keep macros focused and atomic
- Review and update regularly
- Remove unused macros
Related: