ACCELQ View Recorder is a chrome extension used to record and save application page Views. These Views are used for element identification and logic development in ACCELQ. Learn more about how Views augment the test development process in ACCELQ.
Initiating View capture
You can initiate View capture either from the Context home page or the Views section in the Action editor. Click on New View to open a tab selector as shown below.
You can either select one of the currently open tabs (on the browser instance where ACCELQ is open) or type a URL to start recording.
Once you select the tab here, control is automatically transferred to the corresponding browser tab and the ACCELQ Plugin opens. Once the recorder is active, you may even navigate to different pages on the selected tab before starting to record.
Starting to Record
Once the plugin opens, make sure you are in the correct page which you want to record and click on the "Capture View" button.
When the View recording is in progress, plugin window goes to a hidden state. During this process, do not move your mouse or interact with the keyboard.
Once the recording is completed, it will automatically pop back up and prompt you to enter a name for the Context (Page) and the View. Existing Contexts from your project are already listed here. You can choose one of the existing Contexts, or create a new one if required. It is very important you make the right choice and provide a meaningful name to the Context.
Click on the "Add View" button.
At this stage, you can either continue to record more Views or exit the plugin with the currently captured Views.
Based on the application flow or the Scenario you have in mind, it is recommended to capture all the necessary Views in one shot. This will drastically enhance productivity with Action logic development.
To continue recording, simply navigate to the next page in the application that you need to record and repeat the process.
When you start to work with your application screen, the plugin screen is minimized to allow free interaction with your application page. You can click the minimized plugin tab again to open it and start recording.
If there is a need to reach portions of the application screen hidden behind the minimized tab, simply double click on the tab. The tab will hide.
When your cursor moves away from that location, the hidden tab will come back to the display state.
Note: You can capture a maximum of 20 MB size Views per session, which approximately can accommodate about 10 Views. The plugin displays an alert when you are reaching this limit.
Review recorded Views
You can review the currently captured views and make changes to the Context or View name at any point. Click the "Review Views" link in the footer of the plugin screen.
View Recorder Plugin Settings
Following settings are available while recording a View for Web application.
Start capturing from
You can configure to record a View from the top of the application page, or a specific scroll position set on the application page. This is helpful when you are interested to record a specific portion of a page rather than the entire screen from the top. An example of such a requirement is described here.
Number of scrolls to record
Most web pages that you record may have content that extends into multiple page scrolls. With View Recorder, you can record up to a maximum of 5 scrolls per View. This allows you to record a page image that goes multiple scrolls. You can also specify a capture-delay time between each scroll. This will ensure the plugin is waiting for the page to fully load between page scrolls.
Note: You need to capture multiple scroll View only if your test logic requires interacting with elements in those scroll positions. If not, it is better to avoid taking longer Views for enhanced performance. Alternatively, you can also take multiple single scroll Views (instead of a single multi-scroll View) at different points in your application page as described in the setting above. This concept is described in the section below.
Capture with a delay
You can set up an initial delay which is applied after you click on the "Record View" button. During this time, you can perform operations such as mouse-hover, etc. on your application page to bring desired part of your page into visibility. Here is an example.
Note on multi-scroll capture
Most web pages that you record may have content that extends into multiple page scrolls. When you record a View on such a page, the entire DOM from the page is captured regardless of the number of scrolls you are recording. It is only the size of the image snapshot that is limited by the number of scrolls setting.
For example, on a long page such as Search Results on the Amazon website, you may have more than 10 scrolls for the entire page content. But it is not necessary to capture all the 10 scrolls. Depending on which elements you are interested to hover and write the logic in your Action, decide on the minimal number of scrolls to capture, or capture just a specific portion of the page.
Also, when you have a series of similar elements on the screen such as the set of search results, it is sufficient to just record screens to cover one or two search results. DOM structure is recorded in its entirety.
Two options are illustrated below with examples, for a long page with lot of scrolls:
Option 1: Capture multiple scrolls, but just enough number
In the example below, you may just capture 2 scrolls, as the laptop listing is available in the second scroll and the pattern of the laptop listing just repeats itself.
Option 2: Capture page at specific scroll position
Alternatively, scroll the page to a position where the laptop listing is visible and set the Recorder configuration to "Current scroll position". In this case, it is enough just to capture one scroll. There isn't a need to capture multiple scrolls.
Article is closed for comments.