Recording a Scenario Using Record Action Feature

TABLE OF CONTENTS

1. Overview

1.1 How To Use Record Action Feature

1.2 Limitations Record Action Feature

1. Overview

The Record Action feature in the algoScraper extension allows you to capture and record your interactions as a scenario within an application or website in real-time. This feature helps to generate test cases based on the actions you perform.

With Record Action, you do not need to follow the traditional approach of creating an offline model and using the FollowMe feature to record a scenario and generate test cases. Instead, you can directly record your interactions and identify potential test cases. This feature is similar to the FollowMe feature, as both allow you to record scenarios. 

1.1 How To Use Record Action Feature

Perform the following:

1. Access your chrome extension in the status bar. 
2. Click on algoScraper extension.
3. algoScraper window appears. In this window, select Record Action form the More option.
4. Record Scenario window appears. In this window, enter the mandatory fields like scenario name, scenario outline and click on Start Recording button. 
5. Upon selecting the Start Recording button, following screen appears:
   
   1. Icons displayed in the screen are described in the tabular format:
      
      

      Icon	Description
      Edit Scenario	You can view the recorded scenario in a new page.
      Delete	Delete all the UI elements added
      Reset	Reset the UI elements section to default state
      Download	Download the Recorder scenario in CSV and TXT format.
      Start Recording	By default, this icon will be enabled for you to record the scenario. You can stop recording at any point of time by clicking this icon.
      View Scenario	You can view the recorded scenario in a different page.
      Create a Project	As a user, you can navigate to the Project Page using this button after recording a scenario.

      
      
   2. You can click the Add Scenario button to create a new scenario.
      In this window, you can use Reset icon to revert back to the Main window.
6. Perform the actions which has to be recorded as a scenario from your application.
7. Click on Stop Recording button after recording your actions.
   

   Note:Edit out unnecessary steps manually which are recorded while recording actions either in recorder or in profiler.

8. You can download the CSV and TXT file.
9. You can either use algoQA navigation button or upload the downloaded CSV file in the Profiling Page.
   
   

1.2 Limitations Record Action Feature

1. If control name captured in recorder is different from element name like while clicking on checkbox , hovering and  selecting an option from dropdown the name appears different, in this case you have to manually edit the name.
2. In recorder any desktop elements cannot be captured, in this case you can add them manually while profiling.
3. Users cannot capture complete row Xpath, in record scenario if user tries to capture complete row then control name would not be meaningful and if users try to capture correct control names then Xpath will be wrong so in this case manual changes have to be done.
4. Keyboard actions cannot be captured, in this case you can add them manually.
5. If there are two different controls with same name with different control types then control type of first control will be recorded to both the controls, in this case you can manually edit the control type from recorder.

Note: If you choose to re-record a scenario, use the preceding feature, then download the file containing the updated scenario. After downloading, upload the file back into the Profiling to apply the new configuration. Upon the file upload, the new node will be added, while the existing node will remain in place. The new node configuration will take precedence. For more information on how to upload an existing scraped file, refer to the "How to upload existing scraped file".