Here, we explain how to acquire the capture or create test cases when the initial display screen for the browser does not fit on the screen.
Basically, when testing Web browsers, even UI elements that are outside the screen can be automatically scrolled and manipulated, so there is not really any need to be conscious of this when creating test cases. However, some adjustment may be required, depending on the UI elements used and the screen layout.
In order to capture a long vertical screen in one go, click on the small downward pointing triangle button located to the right of the Capture button to activate the "Capture whole page" option. If you click the Capture button in this state, it is possible to scroll through and capture the whole screen.
“Capture whole page” option (Cloud browser/Local PC)
- Horizontal scrolling of the screen is not supported.
- Screens including fixed headers and footers may be inserted multiple times within the capture.
- In the case of types of screens in which elements are dynamically added when you scroll, it is not possible to capture all of the elements.
- In other cases, depending on the screen layout, it may not be possible to capture the entire screen. (for example, cases where only a part of the page scrolls instead of the whole page, or the layout of elements changes when scrolling, etc.)
In case it is not possible to acquire the target UI elements when capturing the whole screen, remove the check from “Capture whole page”, and acquire the capture after scrolling manually until the target elements can be viewed.
・Creating test cases
As described above, after acquiring the capture once, it is not necessary to pay much attention to scrolling. For example, even if you click elements that are off-screen, selecting the "click" command for that element means that the click will be performed after it has automatically scrolled.
However, there are situations in which automatic scrolling will not work.
- In cases where the UI element locator is the AI locator (as in ai=XX)
- In cases where the UI element exists within the scope of the screen, but fixed headers and/or footers are hidden
- In cases where the target element will not be visible unless only a part of the screen, rather than the whole screen, is scrolled
If any of these cases apply, use either
“Continue scroll whole page”
or “Continue scroll UI elements”
before clicking or inputting text, to put the elements you wish to operate in an operational state.
The latter “Continue scroll UI elements” is selected, if you have “3. In cases where the target element will not be visible unless only a part of the screen, rather than the whole screen, is scrolled”. In this example, the element to be displayed for the next operation is "Home (menu)" and the "area(1)" element (sidebar, gadget, etc.) is to be scrolled for that purpose.
As it is difficult to judge whether automatic scrolling is required before running the test, we would recommend creating a test case without scrolling commands and making small adjustments while running the test.