Batch Execution and Configure Custom Tags in algoQA

TABLE OF CONTENTS

1. Overview

2. Configuring the tags for Batch Execution

2.1 Adding Custom tags using Follow Me feature

2.2 Accessing Custom Tags from Edit Scenario Feature

1. Overview

algoQA helps in execution of test cases in batches by allowing you to run multiple test cases together, either sequentially or in parallel.

Before executing the test cases in batches, you need to ensure that all dependencies, such as browser drivers, libraries, and other necessary tools, are installed and configured. They also need to ensure that environment variables are set to access the required resources.

You can execute test cases in batches using the following methods:

• Command Prompt Execution: Navigate to the directory where the scripts are saved and use the appropriate command to run them.

• Jenkins Integration: Integrate with Jenkins, a popular automation server, to schedule and manage the execution of scripts as part of your CI/CD pipeline workflow. For more information, see Executing Scripts using Jenkins Pipeline workflow.

• Third-Party Cloud: You can also execute the scripts in a third-party cloud environment, such as Lambdatest. For more information, see Lamdatest Integration to Execute Web Automation Scripts.

  
  

2. Configuring the tags for Batch Execution

To organize test cases into batches, you can tag each test case with unique identifiers or labels using custom tags. These custom tags can be added while recording a scenario using the Follow Me feature or while editing a scenario in the Edit Scenario feature. 

2.1 Adding Custom tags using Follow Me feature

Perform the following:

1. After logging into algoQA with your credentials, navigate to Main Canvas. 
2. In the Main Canvas, click Follow Me button.
3. Follow Me window appears which allows you to record the scenario, as shown. 
4. In this window, enter Scenario Name, Custom Tag and Scenario Outline as shown and click Create. 
5. Select the respective Node, corresponding features and UI elements and click Submit to record a scenario. For more information on using Follow Me feature, see Profiling - Follow Me feature.
   
   Similarly, while recording the scenarios, you can provide the same tag for each of the scenario.

2.2 Configuring and Accessing Custom Tags from Edit Scenario Feature

Perform the following: 

1. In the Main Canvas, click More to select Edit Scenarios option.
2. If you wish to add a new scenario, you can configure the Custom Tag or if you modifying or adding a GWT step, you can modify the custom tag in the Scenario Form section, as shown:
   
3. In the Edit Scenario window to access the configured tags, select the Filter icon, as shown:
   
4. Following window is displayed for you to select the Filter options. In this window, select the custom tag provided during recording of scenarios. After selecting the required custom tag, all the scenarios related to this custom tag will be displayed.
   
5. Click Close.
6. Navigate back to Main Canvas, click Generate button to generate test cases. For more information on generating test cases, see Profiling - Generate Test Cases article 
7. After generating test cases, click Script Generation button to generate scripts. 
8. Download and extract the scripts generated to your local folder. 
9. Open the command prompt by entering cmd in the address bar of the extracted scripts folder. For more information, see Generate and Execute scripts.
10. If multiple tags are present in the Feature File, such as Login, search and Amazon and if you wish to execute the scripts using Amazon tag, then run the following command:

    mvn test -Dcucumber.filter.tags = "Amazon"