--- title: "Set up tests for test case steps" slug: "set-up-tests-for-test-case-steps" description: "Set up control event procedures for button actions in test cases, defining sequences and conditions for effective testing. Learn how to optimize your tests!" tags: ["Task", "Anywhere Mobility Studio"] updated: 2026-03-20T13:07:28Z published: 2026-03-20T17:46:51Z canonical: "docs.staedean.com/set-up-tests-for-test-case-steps" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.staedean.com/llms.txt > Use this file to discover all available pages before exploring further. # Set up tests for test case steps For a test case step that concerns a button, you can set up a control event procedure with actions that are done in a specific sequence. A control event procedure has one action or a series of actions that are done on the On button clicked control event. So, the procedure is started if the button is clicked. For a test case step event procedure, you can use: - The predefined test actions. - Self-defined test actions - For each of these actions, a self-developed class is required. Use the **Up** and **Down** buttons to define the action sequence. Optionally, you can run an action under specific conditions. For conditions, you can use functions that are available for the application. ### Steps 1. Click **Mobility test manager - Designer**. 2. Click the **Test cases** tab. 3. In the list, find and select the desired record. 4. Click **Edit**. 5. On the **Steps** tab, in the list, find and select the desired step of type **Click** button. 6. Click **Tests**. 7. Click **Edit 'On test button clicked' procedure**. 8. On the **Event procedure** dialog, on the **Actions pane**, click **Add**. 9. Select one or more actions. 10. Click **OK**. 11. On the **Actions pane**, in the list, select an action. 12. On the **Parameters** tab, if available, define the action settings. For a self-defined action, the parameter fields to be set are defined in the related class. 13. You can run an action under specific conditions. Click the **Conditions** tab. 14. Click **Add** and fill in the fields. > [!NOTE] > **Note** > > In the first **Value** field, you can use a test variable, application variable, or a function. In the second **Value** field, you can use a test variable, application variable, a function, or a fixed value. 15. Define the conditions that must be met for the test action to pass. If the conditions are not met, the test fails. You can define the messages that are given when a test is passed or failed. Click the **Asserts** tab. 16. Click **Add** and fill in the fields. > [!NOTE] > **Note** > > In the first **Value** field, you can use a test variable, application variable, or a function. In the second **Value** field, you can use a test variable, application variable, a function, or a fixed value. 17. In the **Passed description** field, enter the message to be given when the test is passed. 18. In the **Failed description** field, enter the message to be given when the test is failed. ## Related - [Define tests for test case steps](/define-tests-for-test-case-steps.md)