Selector: Interface Overview¶
When used with Alyvix Editor rather than as a standalone application, it allows you to quickly select test case objects in order to create scripted interactions.
The Selector interface is centered around a list of all test case objects in a given test case,
with a separate tab for each
primary tab (the first one opened, with the blue background) is the only file whose objects
can be changed. Any other
secondary tabs are used to view and filter their test case objects,
and if desired, to import them into the primary tab. The values of test case objects in secondary
tabs cannot be changed.
You can start Alyvix Selector as a standalone module from the command prompt (you can find information about its command arguments here):
C:\Alyvix\testcases> alyvix_selector -f <file-name>
This will bring up the Selector interface:
The principle interface elements are:
The file tabs show the primary tab and any opened secondary
.alvyixtest case files. Switching between tabs shows the test case objects contained in each file. A new file can be loaded by clicking on the button. Similarly, the button next to a non-primary tab will remove that tab (note that you cannot remove the primary tab).
The list headers categorize the properties of each object, allowing you to sort on some fields and find the details of a particular test case object at a glance.
The test case object list shows the principal properties (excluding the component recognition and interaction settings) of each test case object, with one line for each object.
The list actions let you quickly select or deselect all test case objects in the list, and copy the name of a test case object.
The filtering and search fields let you select all test case objects with a given screen resolution and scaling factor, or that contain a given text string in either the Name or Date modified fields. The Search field uses a non-regex substring search, and the action clears this field.
The test case object buttons, currently selected test case objects in the list. The button will initiate a new screen capture (after a specified in seconds) to define a new test case object., , and act on the
Theand buttons will exit Alyvix Selector, either saving or discarding any changes, respectively.
Selector List Headers¶
The test case object list headers describe the contents of their respective columns. The list can be sorted on the first three columns by clicking on the header name, with the and icons indicating whether the sort order is ascending or descending.
The list headers have the following characteristics:
Name: The object name assigned to the test case object
Transaction group: This is a user-definable field that can be used to group together test case objects that have something in common (for instance a “login” group, “response check” group, “purchase” group, etc.) and then used for sorting and searching
Date modified: The date and time automatically recorded when the test case object was last modified in Designer, Selector or Editor
Timeout, Break, Measure: Displays the values of the corresponding test case object options in Designer
Warning, Critical: The threshold values set for integration with monitoring
Resolution: The horizontal and vertical pixel resolution, and the scaling factor (Windows zoom) of the test case object’s screen capture
The Screen element is a thumbnail of the frame on which that test case object is defined, which can be especially helpful distinguishing between them when you have a large number of objects in a single file
Test Case Object List¶
This list shows all test case objects contained in the
.alyvix file corresponding to the
currently selected tab.
The values for many fields in the primary tab can be changed directly without opening Designer. This can be accomplished by simply clicking on the existing value (or blank space where it should go), entering the new value, and then either pressing Enter or clicking elsewhere in the list.
Remember that in standalone mode, any changes will not be saved until you have exited Selector by clicking on thebutton. When used with Editor, changes from Selector will be saved when the entire test case is saved in Editor.
All editable fields are validated in real time to ensure that only new values of the correct type can be entered. When a value is not valid you will see an error message like this:
The values of test case objects in secondary tabs cannot be changed.
When Selector is being used as part of Alyvix Editor, the and action icons at the start of each row allow you to add the corresponding test case object to the scripting panel by using drag-and-drop or appending it to the scripting panel. The action will execute that test case object as if it were the only scripted element in its test case.
The Shift and Control keys work together with the mouse to select multiple rows in the standard way when using Windows applications. Selected rows are shown with a light blue background, and can then be used with the actions described in the next section below.
Test Case Object Actions¶
option from the command prompt. This action is
available regardless of whether any test case objects are selected.
The allows you to (1) replace the existing screen capture of the current test case object with a new one from the current interface, or (2) add a new screen capture at a different resolution. See the section below for a more complete description.button
The Alyvix Designer with the currently selected test case file and object, allowing you to modify that object.button appears when only a single test case object is selected. Clicking on it launches
Two other actions affect all test case objects currently selected:
will create a new test case object(s) from each selected row. The new name(s) will be the same name(s) as the currently selected object(s), but with the string
_copyappended at the end.
will delete all currently selected test case objects. A confirmation request dialog will appear to make sure test cases aren’t accidentally deleted.
When an additional file tab is open, only theaction will appear. Any objects selected will be copied just as for , except that the new object(s) are copied to the primary tab rather than to the currently opened tab.
Remember that in standalone mode, any changes will not be saved until you have exited Selector by clicking on thebutton. When used with Editor, changes from Selector will be saved when the entire test case is saved in Editor. (No changes will be made to any objects in any secondary tabs).
Regrabbing and Adding Screen Resolutions¶
Thebutton described above has two principal uses, to replace the existing screen capture with a new one, and to add an additional screen capture at a different resolution than the existing one.
When the resolution of the Windows desktop matches one of the resolutions recorded in the test case object, Selector will overwrite that screen capture in the object with the new version.
This replacement allows you to keep a test case up-to-date, which can be useful for times when a web site or web app has been fixed or updated. In addition to simple replacement, you can also use regrabbing to build new test cases faster by using thebutton to copy the test case object, and then just changing the screen.
When the resolution of the Windows desktop does not match any of the screen grabs stored in the test case object, then a grab of the current screen will be added to its existing screen grabs, annotated with the current screen resolution and zoom factor.
When you regrab a test case object that includes a text component in detect mode with a regular expression, the scraped expression will automatically be reprocessed under the existing regular expression and the new value stored.