Common transactions

Look and click

Imagine that your test case has to wait for the arrow button and the main logo of the following webpage and then it has to click on the arrow button to proceed.

../_images/look-and-click_visittrentino_homepage.png

You could build an Alyvix Image Finder keyword: it will measure how much the browser takes to render the button and the logo; then it will click on the button to move on.

The vt_homepage_ready keyword could be an Image Finder which is made as follows:

../_images/look-and-click_visittrentino_homepage_build.png
../_images/look-and-click_visittrentino_homepage_build_02.png

Import the test case library (only one time per test, after a visual keyword creation) and use vt_homepage_ready simply as follows:

../_images/look-and-click_visittrentino_homepage_build_03.png

Fill login forms

Imagine that your test case has to wait for a login form as follows and then it has to fill the form with username and password to proceed:

../_images/fill-login-forms_wuerthphoenix_citrix_login.png

You could build an Alyvix Rect Finder keyword: it will measure how much the browser takes to render the login form; then it will fill the form and click on the Log On button to access the service.

The wp_citrix_login_run keyword could be a Rect Finder which is made as follows:

../_images/fill-login-forms_wuerthphoenix_citrix_login_build.png
../_images/fill-login-forms_wuerthphoenix_citrix_login_build_02.png

Build the keyword and set the password as described in the encryption tool section.

Import the test case library (only one time per test, after a visual keyword creation) and use wp_citrix_login_run simply as follows:

../_images/fill-login-forms_wuerthphoenix_citrix_login_build_03.png

Browse menus and tabs

Imagine that your test case has to select a tab (or a menu) with a certain name as follows:

../_images/menu_tab_select_visittrentino_homepage.png

You could build an Alyvix Object Finder keyword, made of an Image Finder as main component and a Text Finder as sub component. The image component should include the close button, which is present on each tab, as the main component and some fixed icons, which are always shown in the bar below, as sub components to disambiguate the detection.

../_images/menu_tab_select_visittrentino_homepage_build.png

The text component should include all the available space for text in a tab as its ROI. Set an argument to enable the selection of a certain tab with a given name.

../_images/menu_tab_select_visittrentino_homepage_build_02.png
../_images/menu_tab_select_visittrentino_homepage_build_03.png

Join the image and text components in an Object Finder.

../_images/menu_tab_select_visittrentino_homepage_build_04.png

Import the test case library (only one time per test, after a visual keyword creation) and use chrome_tab_select simply as follows:

../_images/menu_tab_select_visittrentino_homepage_build_05.png

Moreover if your test case has to select a menu item in a fixed position, you could build an Alyvix Image Finder with two interaction on the same selected element (i.e. the menu button): a first click to expand the menu and a second displaced click to select the menu item.

../_images/menu_tab_open_visittrentino_homepage_build.png
../_images/menu_tab_open_visittrentino_homepage_build_02.png

Import the test case library (only one time per test, after a visual keyword creation) and use chrome_window_open simply as follows:

../_images/menu_tab_open_visittrentino_homepage_build_03.png