Test Case Building

When you build a test case , you’re creating a set of visual templates that can be matched against your app interfaces in real time, allowing Alyvix to interact with those interfaces just like a person would.

When setting up Alyvix to work with your applications, you will spend most of your time creating test cases and their test case objects, so it’s worth some time to learn how to do it the right way and understand from the beginning what the available options are.

There are three main tools for building test cases:

1. Alyvix Designer: Define individual test case objects to be dynamically matched against the visual components of your app’s interface, and assign GUI actions that are carried out when those matches are detected

2. Alyvix Selector: Easily manipulate (inspect, copy, edit, delete) large numbers of test case objects created with Designer, as well as view, filter and sort their properties

3. Alyvix Editor: Create scripts using test case objects (as sequential execution units, conditionals, and loops) to interact with any app according to complex behaviors you define

For most use cases, Alyvix Editor (which includes Designer and Selector) is all you’ll need. But if required, Designer and Selector can also be run as separate modules.

Once you’ve built a test case, you can let it interact with your chosen app either by using Alyvix Robot, or testing it directly within Editor.

The Test Case Data Format page provides technical details on how Alyvix test case files are organized and what they contain, while the Getting Started and Videos and Tutorials sections include detailed mini-tutorials and topic-based videos on how to use Alyvix Editor and Robot.

All of the Alyvix applications can be launched from the Windows Command Prompt or PowerShell. Note that they inherit the permissions of the shell they were launched from.

Alyvix Designer

Alyvix Designer lets you select graphic components on a captured screen to use as test case objects, whether they’re images, rectangles, or text. You can then define triggers and actions to apply when those templates are recognized later in a live interaction with an application.

Designer will save the set of templates, called the component tree as a single test case object, which you can then use as a building block to compose more complicated behaviors with scripts using Alyvix Editor.

The following sections of the guide present further information on Alyvix Designer:

• The Designer Interface Overview page provides a high-level overview and describes the general layout of the interface

• The Component Tree page describes the specific test case object types available, including what they can do and how to interact with them

• You can find more detailed information about the available options for test case objects and components on the Interface Options page

Although it is typically run together with Alyvix Editor, Designer can be run in standalone mode as follows:

C:\Alyvix\testcases> alyvix_designer

with the following command line options:

Option	Alias	Argument	Description
--delay	-d	<n>	Wait n seconds before grabbing the screen, giving you time to move windows around
--filename	-f	<name>	Supply the file name with no extension
--object	-o	<name>	Supply the Object name
--verbose	-v	<n>	Set the verbosity level for debugging output ranging from 0 (min) to 2 (max)

Alyvix Selector

Alyvix Selector is used to centralize the management of all of your test case objects, such as exporting them to other Alyvix files. It also provides options to view, copy, edit and delete test cases objects.

Selector is organized as a set of tabbed panels representing one or more test case files, and a list of test case objects within each tab. This allows you to quickly switch between them and filter, search and edit within a single file, or copy test case objects across opened test case files.

Although it is typically run together with Alyvix Editor, Selector can be run in standalone mode as follows:

C:\Alyvix\testcases> alyvix_selector

with the following command line options:

Option	Alias	Argument	Description
--filename	-f	<name>	Supply the file name with no extension
--verbose	-v	<n>	Set the verbosity level for debugging output ranging from 0 (min) to 2 (max)

Alyvix Editor

Alyvix Editor helps you create scripts using the individual test case objects in a single test case file, and allows you to create more complex interactions compared to using Designer alone.

The following sections of the guide present further information about Alyvix Editor:

• The Editor Interface Overview page describes the layout of the panels and how to use the interface controls

• The Scripting Management page shows you how to manipulate (view, copy, edit, delete) the scripts and scripting components you have created

• The Scripting Panel page explains how to create scripted interactions between existing test cases

Alyvix Editor can be run as follows:

C:\Alyvix\testcases> alyvix_editor

with the following command line options:

Option	Alias	Argument	Description
--filename	-f	<name>	The test case file name (with no extension)
--verbose	-v	<n>	Sets the verbosity level for debugging output ranging from 0 (min) to 2 (max)

• Editor: Interface Overview
  • Editor-Specific Features
  • The Test Case Menu
  • The Monitor Tab
  • Launching Alyvix Robot from Alyvix Editor
• Editor: Managing Scripts
  • Top level Scripts
  • Sections
  • The Map Interface
  • Debugging Scripts
• Editor: Script Building
  • Adding Scripting Nodes
  • Script Expression Modes
  • Scripting Node Colors
  • Scripting Node Actions
• Designer: Interface Overview
  • Selections, Subselections and Regions of Interest
  • Returning from Screen Capture Mode
  • Interface Controls
• Designer: Interface Options
  • Test Case Object Options
  • Component Options
    • Root Component Options
    •     Image Type Options
    •     Rectangle Type Options
    •     Text Type Options
    • Common Options
      • Mouse and Keyboard Action Icons
  • The String Field
    • Escaped String Examples
    • Special Characters
• Designer: Component Tree
  • Structure of the Component Tree
  • Object Recognition Types
  • Creating Groups and Components
  • Component Tree Actions
• Selector: Interface Overview
  • Selector List Headers
  • Test Case Object List
  • Test Case Object Actions
  • Regrabbing and Adding Screen Resolutions
  • Interactions - Timeout, Measure, Break