Using Follow Me

TABLE OF CONTENTS

1. Overview

2. Editing a recorded scenario

3. Adding Assertions

4. Editing the UI elements

1. Overview

Follow Me feature helps you in recording a scenario. 
In the Follow Me feature, you can:

• record a scenario. To do this, follow the instructions provided in Record a scenario using Follow Me feature.
• use custom tags. To do this, follow the instructions provided in Batch Execution and Configure Custom Tags.
• edit a recorded scenario. 
• add assertions
• edit a UI element

2. Editing a recorded scenario

Perform the following:

1. Navigate to Main Canvas and click Follow Me button.
2. In the Follow Me pop-up window, Enter the scenario name, outline the steps briefly, and click Create to create a sequence. 
3. Create Profile Sequences pop-up window appears. All the available nodes are listed in the window. In this window, select the required node, required feature and UI elements.
4. Click OK and Close. Scenario workflow has been recorded. 
5. If you choose to edit the recorded scenario, then click the edit icon in the 'Edit created scenario pane' to view the Edit Scenario window. Make sure that you perform this action before clicking the Submit button. For more information, see Managing Test Cases using Edit Scenario Feature. 

3. Adding Assertions

Perform the following:

1. Repeat the step 1 and step 2 from the preceding section.
2. Create Profile Sequences pop-up window appears. All the available nodes are listed in the window. In this window, select the required node, required feature and UI elements. While adding UI elements, you can select the default action as 'wait in seconds' to the UI element to appear.
   For example, after you wait for a UI element like a button to appear, you can use an assertion to verify that the button is visible or clickable.
   • Action: Wait for 5 seconds for the button to appear.

   • Assertion: After waiting, the test checks if the button is visible on the page.

     This combination of wait and assertion ensures your test only proceeds when the element is ready and confirms it is working as intended.

3. Click OK and Close. Scenario workflow has been recorded. click Submit to save the changes.

4. Editing the UI elements

Perform the following:

1. Repeat the steps 1 and 2 from the Editing a recorded scenario section.
2. Create Profile Sequences pop-up window appears. All the available nodes are listed in the window. In this window, select the required node, required feature and UI elements. While selecting UI elements, click the Edit icon aligned with UI element line item. Edit Control pop window appears for you to add a new name (alias name) for an existing UI element.
   In this window, click Show More link to expand the details of the UI elements.
   The following table provides the Edit Control pop-up window details: 
   

   Field	Description
   Alias Name	If you choose to add a new name or modify an existing name for an UI element or a Control, then you can use this text box. You can add Alias name in the Follow Me feature too.
   Default/Custom Action	Default actions are the ones readily available as part of automation framework in algoQA.  algoQA platform allows you to create custom actions to incorporate your application specific  testing requirements. You can select the default/custom action from the drop down list.  For more information, For more information on Default Actions, refer to Default Actions  and For more information on Custom Actions, refer to Custom Actions.
   TestStep Settings	You can select specific condition or a parameter from the dropdown list. Allows you to customize your test steps by selecting or excluding specific conditions, ensuring that only relevant steps are included. For example, if you wish to avoid generating the default post-condition step, you can select the 'No Postcondition' option from the dropdown. This will prevent the default last step from appearing in the Feature File.
   GWT Input	To add a prefix to a  GWT step, then you can update the textbox. By default, the initial context in a Given step is shown as "I".   For example, 'Given I have access to application' sets up the initial state for the test.
   Custom Value	You can provide user-specific value, keywords and parameters in the custom value text box. It will be reflected in the Feature File. For more information, see  Keywords Used in algoQA and Their Descriptions. When entering a value in the custom value field, adhere to the following:  Custom value cannot be just blank spaces. If you wish to include spaces, you can use the keyword _empty_. For more information, see Keywords used in algoQA. If you hit spacebar to enter only spaces, then following error message is displayed: You can include spaces at the beginning, end, or between words.
   Message	You can provide a comment or text for a particular GWT step. When entering a value in the message field, adhere to the following:  Message field cannot be just blank spaces. If you wish to include spaces, you can use the keyword _empty_. For more information, see Keywords used in algoQA. If you hit enter only spaces, then following error message is displayed: You can include spaces at the beginning, end, or between words.