AppVerify 1.1

Transcription

AppVerify 1.1

App erfiy
Version 1.1
www.nrgglobal.com © NRG Global, Inc.
USER GUIDE: AppVerify 1.1
Contents
INTRODUCTION TO APPVERIFY .............................................................................................................................4
APPVERIFY ARCHITECTURE ...........................................................................................................................................5
BEFORE THE INSTALLATION ...................................................................................................................................6
INSTALL APPVERIFY SUITE......................................................................................................................................7
PREREQUISITES ..............................................................................................................................................................7
INSTALL APPVERIFY CONTROLLER ...............................................................................................................................7
INSTALL RTESTER ....................................................................................................................................................... 12
INSTALL SCENARIOBUILDER ....................................................................................................................................... 17
END USER LICENSE AGREEMENT.................................................................................................................................. 21
BASIC TERMINOLOGY ............................................................................................................................................. 23
CREATE A SCENARIO USING SCENARIOBUILDER .......................................................................................... 24
LAUNCH APPVERIFY CONTROLLER.................................................................................................................... 27
DASHBAORD............................................................................................................................................................... 30
MANAGE TEST PLANS.............................................................................................................................................. 32
CREATE NEW TEST PLAN ............................................................................................................................................ 33
Plan ......................................................................................................................................................................................... 34
Scripts .................................................................................................................................................................................... 36
Data ......................................................................................................................................................................................... 37
Test cases .............................................................................................................................................................................. 41
Expected outcome.............................................................................................................................................................. 44
Publish ................................................................................................................................................................................... 55
GENERATE TEST PLAN RUN ....................................................................................................................................... 58
VIEW TEST PLAN RUN REPORT .................................................................................................................................. 65
EDIT TEST PLAN ......................................................................................................................................................... 67
DELETE TEST PLAN .................................................................................................................................................... 68
MANAGE REPORTS ................................................................................................................................................... 69
Latest Test Plan Run report ........................................................................................................................................... 70
Test Plan Run summary report..................................................................................................................................... 73
© 2015 NRG Global, Inc. All rights reserved.
Page 2
VIEW RTESTERS ........................................................................................................................................................ 75
MANAGE PROJECTS .................................................................................................................................................. 77
MANAGE USERS ......................................................................................................................................................... 78
USERS .......................................................................................................................................................................... 78
Create new user .................................................................................................................................................................. 79
Edit user ................................................................................................................................................................................ 80
Delete user ........................................................................................................................................................................... 80
GROUPS ....................................................................................................................................................................... 81
Create new group ............................................................................................................................................................... 81
Edit group ............................................................................................................................................................................. 82
Delete group ........................................................................................................................................................................ 82
USER PROFILE............................................................................................................................................................ 83
User information ................................................................................................................................................................ 84
User preferences ................................................................................................................................................................ 87
SETTINGS ..................................................................................................................................................................... 89
Test Plan options ............................................................................................................................................................... 89
APPENDIX.................................................................................................................................................................... 91
API SPECIFICATION ..................................................................................................................................................... 91
Methods ................................................................................................................................................................................. 91
GETTING HELP........................................................................................................................................................ 100
INDEX ......................................................................................................................................................................... 101
Page 3
Introduction to AppVerify
Regression testing represents an important part of the overall test effort on each application release. It is
required because it can find problems that have been undetected upstream. However with manual testing there
is a high rate of missed bugs which are found after deployment when the cost to fix them is usually estimated to
be at least 10 times higher. With the possibility to eliminate of hundreds of bugs and to reduce the time
expended in regression testing, automated regression testing is an obvious choice.
AppVerify is a unique solution for automated regression testing. With AppVerify, you can test the functionality
of any application or website in any environment. Our powerful tool makes it easy to create a list of Test cases,
allowing you to re-execute your Test Plans as often as you like, to verify that modifications in the application or
the environment have not caused any unintended adverse side effects and that the system still meets its
requirements.
AppVerify gives you the answers to the following questions:

How many user Test scenarios/ Test cases have been executed?

Does the app give out correct error messages if the user does not use it the way it was intended to
be used?

Which features need more work?

Do application response times meet your target requirements?

What is the quality of the application? Is it ready to ship?
Test More, Test Faster
AppVerify boosts your testing team efforts to test more and test faster through:
 Simplifying the process of generating automated Test Plans for all parts of an application or a website by
creating various Test cases.
 Automatically testing all your Applications without buying and installing any additional software or
plugins.
 The ability of viewing the test results and failures screenshots instantly.
 A smart solution to help you to save your time and money by improving the quality of your software and
your customers' satisfaction.
Click here to watch AppVerify product overview video.
Page 4
AppVerify architecture
AppVerify Controller
Create Test scenarios
ScenarioBuilder
Send scripts
 Easy Testing
 More Testing
 Faster Testing
Create Test cases
Test
case 1
Test
case 2
Test
case 3
Test
case 4
Build Test Plan
Test Plan
Generate Test Plan Run
Test
case 5
Test
Plan
Run
Test
Plan
Run
Report
•••
Play Test Plan Run
rTester 1
rTester 2
rTester 3
Send the results and create Test Plan Run report
Page 5
Before the installation
The AppVerify Suite consists of three components – AppVerify Controller, rTester, and ScenarioBuilder.
Together, they comprise NRG Global’s automated regression testing solution.
Install the AppVerify components in the following manner:
1. AppVerify Controller – Install on a Windows PC or Windows Server. Installation sets up the Controller
in which Test Plans are built, managed and executed. It also generates summarized and detailed test
results and reports.
2. rTester – Install on a Windows PC or Windows Server. The robot that executes the Test Plans
configured in the AppVerify Controller.
Make sure that AppVerify Controller is already installed before installing the rTester.
3. ScenarioBuilder (version >= 8.1) – Install on a Windows PC or Windows Server. This easy-to-use tool
facilitates the creation of a wide range of Test scenarios for regression testing.
AppVerify components can be installed on either Physical or Virtual machine(s).
Page 6
Install AppVerify suite
Prerequisites
Start by downloading the AppVerify installation package from the Downloads page on the NRG Global
website. Save the AppVerify_suite_setup.zip file to your Windows PC or Windows Server and extract the contents
of the file to a new folder. You will find a separate folder for each of the components; AppVerify, rTester and
ScenarioBuilder. Within each folder is a setup file for its respective component.
1.Install AppVerify Controller
These are the steps to install AppVerify Controller:
1. Run the AVSetup.exe file in the AppVerify folder.
Page 7
2. Click “Next” to advance to the “End User License Agreement” (EULA).
Review the terms of the EULA and click “I accept the agreement” and click “Next” to continue.
3. Select the destination folder for the AppVerify program installation. Click “Next” to accept the default
location or “Browse” to an alternate location, then click “Next.”
Page 8
4. Enter the web server configuration and click “Next”. (Choose the default unless it is used by other
applications. “Web Server Port : 8888”)
Page 9
5. Review settings and click “Install” to initiate the installation process.
Page 10
6. Click “Finish” to complete the AppVerify Controller installation.
Page 11
2. Install rTester
1. Run the rTesterSetup.exe file in the rTester folder.
Page 12
3. Select the destination folder for the rTseter program installation. Click “Next” to accept the default
location or “Browse” to an alternate location, then click “Next.”
4. Enter the hostname of the Server where the AppVerify Controller is located.
Enter the “AppVerify Web Server Port” address – use the same port that was assigned to the AppVerify
“Web Server Port” in the AppVerify installation. (Choose the default one: “Web Server Port: 8888”), then
click “Next”.
Page 13
5. The rTester setting will be configured automatically, Click “Next.”
Page 14
Page 15
7. Click “Finish” to complete the rTester installation.
Once installed, the rTester will start automatically. But if it does not start, you can start it from the
rTester’s folder in program menu or by using the desktop shortcuts.
In order to add a new rTester, click the “Add New rTester ” button from the rTester’s folder in program
menu and then follow the instructions to add a new rTester.
Page 16
3. Install ScenarioBuilder
1. Run the SBSetup.exe file in the ScenarioBuilder folder.
Page 17
3. Enter the IP address of the server hosting the Controller (if using with AppVerify) in the “Host Name”
field.
Enter the “Port Number” address – use the same port that was assigned for “Web Server Port” in the
Controller/Base installation. (Choose the default one: “Port Number : 8888” ), then click “Next”.
4. Select the destination folder for the ScenarioBuilder program installation. Click “Next” to accept the
default location or “Browse” to an alternate location, then click “Next.”
Page 18
If upgrading from an older version or reinstalling the current version of ScenarioBuilder, the
windows for steps 3,4 will not appear – prior settings will be used.
Page 19
6. Click “Finish” to complete the ScenarioBuilder installation.
Page 20
End user license agreement
IMPORTANT -- PLEASE READ CAREFULLY BEFORE USING THIS SOFTWARE PRODUCT: This End-User
license Agreement ("EULA") is a contract between (a) you (either an individual or the entity you represent) and
(b) NRG Global, Inc. ("NRG GLOBAL") that governs your use of the software product (“Software”).
RIGHTS IN THE SOFTWARE ARE OFFERED ONLY ON THE CONDITION THAT YOU AGREE TO ALL TERMS AND
CONDITIONS OF THIS EULA. BY INSTALLING, COPYING, DOWNLOADING, OR OTHERWISE USING THE
SOFTWARE, YOU AGREE TO BE BOUND BY THIS EULA. IF YOU DO NOT ACCEPT THIS EULA, YOU MUST
DESTROY ALL COPIES OF THE SOFTWARE AND ACCOMPANYING DOCUMENTATION WITHIN 1 DAY OF
PURCHASE FOR A REFUND FROM NRG GLOBAL.
1. THIRD PARTY SOFTWARE. The Software may include, in addition to NRG GLOBAL proprietary software
(“NRG GLOBAL Software”), software under licenses from third parties (“Third Party Software” and “Third Party
License”). Any Third Party Software is licensed to you subject to the terms and conditions of the corresponding
Third Party License. Generally, the Third Party License is located in a file such as license.txt or read.me file; you
should contact NRG GLOBAL support if you cannot find any Third Party License.
2. LICENSE RIGHTS. You will have the following rights provided you comply with all terms and conditions of this
EULA: a. Use. NRG GLOBAL grants you a license to Use one copy of the NRG GLOBAL Software. "Use" means
installing, copying, storing, loading, executing, displaying, or otherwise using the NRG GLOBAL Software. You
may not modify the NRG GLOBAL Software or disable any licensing or control feature of the NRG GLOBAL
Software. Additional restrictions on Use may appear in the User Documentation. You may not separate
component parts of the NRG GLOBAL Software for Use. You do not have the right to distribute the NRG GLOBAL
Software. b. Copying. You may copy the NRG GLOBAL software for back-up and archival purposes, provided any
copy contains all the original software’s proprietary notices.
3. UPGRADES. To Use NRG GLOBAL Software provided by NRG GLOBAL as an upgrade, update, or supplement
(collectively “Upgrade”), you must first be licensed for the original NRG GLOBAL Software identified by NRG
GLOBAL as eligible for the Upgrade. To the extent the Upgrade supersedes the original NRG GLOBAL Software,
you may no longer use such NRG GLOBAL Software. This EULA applies to each Upgrade unless NRG GLOBAL
provides other terms with the Upgrade. In case of a conflict between this EULA and such other terms, the other
terms will prevail.
4. TRANSFER. a. Third Party Transfer. The initial end user of the NRG GLOBAL Software may make a one-time
transfer of the NRG GLOBAL Software to another end user. Any transfer will include all component parts, media,
User Documentation, this EULA, and if applicable, the Certificate of Authenticity. The transfer may not be an
indirect transfer, such as a consignment. Prior to the transfer, the end user receiving the transferred Software
will agree to this EULA. Upon transfer of the NRG GLOBAL Software, your license is automatically terminated. b.
Restrictions. You may not rent, lease or lend the NRG GLOBAL Software or Use the NRG GLOBAL Software for
commercial timesharing or bureau use. You may not sublicense, assign or otherwise transfer the NRG GLOBAL
Software except as expressly provided in this EULA.
5. PROPRIETARY RIGHTS. All ownership and intellectual property rights in the Software and User
Documentation are owned by NRG GLOBAL and/or its suppliers and are protected by law, including applicable
Page 21
copyright, trade secret, patent, and trademark laws. You will not remove any product identification, copyright
notice, or proprietary restriction from the Software.
6. LIMITATION ON REVERSE ENGINEERING. You may not reverse engineer, decompile, or disassemble the NRG
Global Software, except and only to the extent that the right to do so is allowed under applicable law.
7. CONSENT TO USE OF DATA. NRG Global and its affiliates may collect and use technical information you
provide in relation to (i) your Use of the Software or the NRG GLOBAL Product, or (ii) the provision of support
services related to the Software or the NRG GLOBAL Product. All such information will be subject to NRG
GLOBAL’s privacy policy. NRG GLOBAL will not use such information in a form that personally identifies you
except to the extent necessary to enhance your Use or provide support services.
8. LIMITATION OF LIABILITY. Under no circumstances shall NRG GLOBAL or its suppliers or resellers be liable
to licensee or any other person for any special, incidental, indirect, or consequential damages, including
damages for loss of goodwill, lost profits, work stoppage, business interruption, personal injury, computer
failure, loss of privacy, or any and all commercial damages or losses, even if NRG GLOBAL or any supplier has
been advised of the possibility of such damages. Further, in no event shall NRG GLOBAL’s liability under any
provision of this agreement exceed the license fee paid to NRG GLOBAL. Some states or other jurisdictions do
not allow the exclusion or limitation of incidental or consequential damages, so the above limitation or
exclusion may not apply to you.
9. U.S. GOVERNMENT RESTRICTED RIGHTS AND COMPLIANCE WITH EXPORT LAWS. This software is provided
with RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government is subject to restrictions as set
forth in subparagraph (c)(1)(ii) of The Rights in Technical Data and Computer Software clause of DFARS
252.227-7013 or subparagraphs (c)(i) and (2) of the Commercial Computer Software-Restricted Rights at 48
CFR 52.227-19, as applicable. You will comply with all laws, rules, and regulations (i) applicable to the export or
import of the Software, or (ii) restricting the Use of the Software.
10. RESERVATION OF RIGHTS. NRG Global and its suppliers reserve all rights not expressly granted to you in
this EULA.
Page 22
Basic terminology
The following terms are commonly used in AppVerify and are discussed in detail throughout this guide:
AppVerify Controller: The central console from which Test Plans are built, managed and executed. It also
generates summarized and detailed test results and reports.
ScenarioBuilder: The tool for creating sequences of user actions on the application under test.
rTester: The robot that executes the Test Plans configured in the AppVerify Controller.
Test scenario: A Test scenario is a set of instructions performed on the AUT (Application Under Test) to test
that the application functions as expected. A Test scenario can have multiple sub-scenarios.
Test case: A Test case is a sequence of test steps that form a single test. This is usually the smallest unit of
testing. A Test case will consist of information such as test variables, conditions , detailed steps, verification
steps, prerequisites, outputs, and etc. Each Test case should focus on only one requirement or condition.
Test Plan: A Test Plan is a collection of Test cases and the sequence in which they are to be executed.
Test Plan Run: A Test Plan Run is created every time a Test Plan needs to be executed and consists of multiple
Test cases. They also include test results and are closed after the specific test is performed.
Page 23
Create a scenario using ScenarioBuilder
Scenarios are the action sequences which emulate your real user activity within your application and are
used by AppVerify solution for Regression testing. Creating your first scenario is simple. If you know how to use
your application, then you know how to script a scenario with ScenarioBuilder.
Double-click the ScenarioBuilder shortcut
to launch the splash screen.
The ScenarioBuilder “Splash Screen” greets you upon launching the program. Here, you may create a new
Scenario, open an existing Scenario, or familiarize yourself with the common Actions used in ScenarioBuilder.
We recommend creating scenarios using SSrdpManager so there will not be any differences between the
scenario creation environment and the regression testing environment.
Once the Scenario is complete, do the following steps:
1. Playback scenario (as many times as necessary) to ensure that it performs as expected.
Page 24
2. Set reference time (in execution report window after a successful scenario playback).
Set the reference time
3. Save scenario.
4. Send it to the AppVerify Controller.
You will see a dialog box indicating “Send successful” upon completion.
Page 25
To make sure that the scenario will be sent to the correct controller, you can follow these steps:
1.
2.
3.
4.
Click on “View” in ScenarioBuilder toolbar
Go to “Option”
Click on “Base”
If you couldn’t find the Controller address, click on the “Add” button to enter your AppVerify Controller
information.
5. Click on “Test” button to test the connection between ScenarioBuilder and AppVerify Controller.
5. Close or minimize ScenarioBuilder.
Please refer to the ScenarioBuilder User Guide for more information. You can download it here.
Click here for the complete ScenarioBuilder video tutorial series.
Page 26
Launch AppVerify Controller
After creating and sending your Scenario(s), launch the AppVerify web interface to create, run and
manage your Test Plans. After installing AppVerify, a shortcut will be created on the desktop. Launch the
AppVerify Controller by:
Double-click the AppVerify shortcut to launch the Controller in your default browser.
You can also launch the AppVerify Controller by entering IP address of the PC/Server (or “localhost”) and
Web Server Port number into the address bar of a web browser.
Log in to AppVerify Controller (Default: Username: admin / Password: admin)
Put the correct login credentials and press “Enter”
Page 27
The AppVerify Controller defaults to the “Dashboard” page upon opening.
Take some time to get familiar with the interface before you start working with AppVerify.
Menu Bar
Left Pane
Expand the Manage Users to see
the Users and Groups sections
In the AppVerify Controller default view, you will see the “Menu Bar” across the top of the page that gives you
access to the Alerts, Help and Log out options. And the “Left Pane” which is organized into a number of sections.
It provides a guide to creating, running, analyzing and managing your Test Plans. The “Dashboard” section
remains open throughout your session. Subsequent pages viewed during your session will open in new pages.
Page 28
#
Use to:
1
View User profile and the last login date and time.View AppVerify version information.
2
Create and manage Test Plans , perform Test Runs and view test results.
3
Main Panel
4
Update/Upgrade Avaliable notification
5
View rTesters status
6
View AppVerify UserGuide, AppVerify tutorial, License Agreement and About page.
7
Log out of the AppVerify Controller and return to the login page.
Page 29
Dashbaord
The dashboard is the main interface you see when you login to the AppVerify
Controller. It is useful for tracking the status of the latest test results by groups
and projects and analyzing the data collected in a project. A dashboard also provides you with immediate access
to a gallery of screenshots showing images from actual desktops, captured at the time of failures.
Some information about the screenshot
Once you click on one group, it will show you the screenshots of that specific group.
Group
Click to view larger
Page 30

Click on image for larger view.
Click to open image in a new tab
Page 31
Manage Test Plans
This section provides options for creating Test Plans, modifying, generating and
executing Test Plan Run.
To open the “Manage Test Plans” page, simply click the “Manage Test Plans” button in the left pane of the
AppVerify. Here you can see the list of all Test Plans and basic information about them. The list gives you the
options to generate Test Plan Runs, view Test Plan Run report, edit, and delete Test Plans.
From this list, you can see which Test Plans are locked and which are ready to be generated.
Locked Test Plan means that the Test Plan is still in “draft” mode and it is not published yet by the user. In
this case the other users cannot access them.
Start typing to find a Test Plan
Test Plan is not published
Locked Test Plan

Use the filter
to search a Test Plan by Test Plan name.
During the creation process if any change is made in the Test Plan or Test case (add, delete, edit, etc), all the
updates will be saved automatically.
Page 32
Create new Test Plan
To create a new Test Plan, click on “Create New Test Plan” button
next to the “Test Plans List” text.
Go to Manage Test Plans and click on +
Once you click on it, the “Build Test Plan“ form will be opened;
The above image shows how the Test Plan form looks upon opening. Next, we will break down each section of
the form and provide an image with typical sample data entered, per section:
Page 33
Plan
Specify a name and
select a project
Choose a group
and click on Next
Test Plan: A unique name used to identify this Test Plan. (Use standard alpha/numeric characters only.)
Test Plan is created when you would like to execute Test cases. Test Plans can be made up of the Test cases
from different scripts.
In order to save the Test Plan you must enter a name for it.
Project: Select a project that this Test Plan applies to.
Groups: Select a project group to associate in the project. You can choose multiple groups.
Selected Groups: The selected groups will automatically appear here.
Initialize Test Plan with (Optional): Select a script that will run before any scripts in the Test Plan Run.
Finalize Test Plan with (Optional): Select a script that will run after the rTester finishes executing the
script(s) in the Test Plan Run.
Initialization and finalization scripts are similar to other scripts. The purpose of these scripts is to perform
one-time initialization routines upon Test Plan Run starts (such as launching Web Browser, loading website,
login to application, etc.) and finalization routines (properly close application, cleanup and release memory or
other resources) upon Test Plan Run finishes.
Description: Enter an optional description of the contents of the Test Plan. You can enter up to 255 characters.

The project groups can be deleted by clicking on
Next, click on
button.
button next to the desired group to continue.
Page 34
Stop on error:
During a Test Plan Run, you may need to interrupt the entire Test Plan Run after an error occurs in the Test
Plan. In order to do this, use the Test Plan’s “Stop on error” option. By default, this option is disabled so that
whenever an error is encountered, AppVerify simply continues running the test until it gets another command.
When the test is over, you will be able to view all the errors that occurred during the Test Plan Run in the Test
Plan Run report.

To enable this option, check the
option.
When the option is enabled
and an error occurs, AppVerify will continue the Test Plan Run until the current
script is over. And then it will stops the Test Plan Run.
Stop on error in the Test Plan
Do not confuse this option with the “Stop on error” option for the scripts. For more information, see Test
cases section.
If you try to create a Test Plan in the AppVerify Controller before sending the script to the Controller, a
message pop up will be displayed as below:
Page 35
Scripts
Choose a script and click on Next
Project Script: Select the project script you want to execute. You can choose multiple scripts.
Selected Scripts: The selected project scripts will automatically appear here.

The project scripts can be deleted by clicking on
Next, click on
button.
button next to the desired script to continue.
AppVerify gives you the option to to change the order of Test Plan scripts in a group by clicking on
Up/Down icons.
Click on Up/Down icons to sort scripts
Page 36
Data
Choose a variable,
put a variable state
and a variable value
Test variables are attributes (scenario parameters) of the tested application used to generate Test cases. They
can be used to create multiple Test cases from a script to support various configurations. Create a Test case to
define the set of conditions, actions, expected results, and other criteria used to determine if an application
works correctly and meets its specified requirements.
Variable Name: Select a variable associated with the script.
Variable State: Specify the state of the variable. The variable state is part of the Test case name. Each variable
in your script may have multiple data states.
Variable Value: Enter your variable value as follows:

Simply type in your value.

Pre-defined variable: Double-click on the textbox to be able to select your pre-defined variable. Options
include date and time in different formats and unique numbers.
For date and time pre-defined variable values, the default values are always based on current date and
time. However, you can add or subtract values from the individual month, date, year, hour, minute or
second. For example, [MM+1/dd/yy], [MM/dd-1/yyyy], [hh-1:mm:ss].
Do not remove the beginning and ending brackets from the pre-defined values; multiple modification
(addition, subtraction) are allowed per variable value.
Page 37

To add the variable to the Test Plan, Click on
button.
The variables can have empty values. Once you put empty value in the “Variable Value” textbox, it will be
displayed as “empty value”.
Empty value



To edit each variable select and edit the variable and then click on
To delete the variable click on
button.
To reset the changes, click on
button.
button to apply the changes.
You are not allowed to delete the Variable state for the Default Test case but you can modify the variable
value.
If you try to create duplicate vraibale states, AppVerify will overwrite the variable value.
Page 38

To export variables click on
button. AppVerify will export script variables to the specified .xls file.
Exported Variables File

To import variables click on
button. The “File Upload” dialog box will appear over the active window.
Select the desired xls/csv file, then click on open.
Select the desired file and click
on “Open” to upload the file
Page 39
Once you import the correct file, you will see the new data.
Please remember data elements format have to be similar to the exported file. Otherwise, you will get the
following error message.
After adding all the necessary variables, click on “Generate Test cases”
button.
Click to generate Test cases
Once you click on it, a message pop up will be displayed;
Page 40
To generate new Test cases, click on “Generate”
Click on “View Existing Test cases”
button.
button to see the previous Test cases.
Test cases
Here you can see the list of all Test cases that have been created on the previous section. From this list, you can
go through every Test case and edit or delete them.
Expected result for each Test case
Click to delete the Test case
Click to add a new Test case
Page 41

To edit the Test case, click on each variable you want to modify and make the changes.
Click to edit the Test case

To delete the Test case, click on

To create a new Test case and add it to this Test Plan, click on
button.
button.
Enter the details for your new Test case including the variables and the values.
Specify a name for the Test case
Stop on error:
During a Test Plan Run, you may need to interrupt the entire Test Plan Run after an error occurs in the script(s).
In order to do this, use the script’s “Stop on error” option. By default, this option is disabled so that whenever
an error is encountered, AppVerify simply continues running the test until it gets another command. When the
test is over, you will be able to view all the errors that occurred during the Test Plan Run in the Test Plan Run
report.

To enable this option, check the
button.
When the option is enabled
and an error occurs, AppVerify will stop running the script but it will continue
playing the other scripts of the Test Plan Run.
Page 42
Stop on error in the script
When all the Test cases in a Test Plan have been generated, the Test Plan can be moved to its final step.
Click to go to the “Expected outcome” section
Next, click on
button.
Page 43
Expected outcome
In this section you can see the Test scenarios steps (actions) which will be performed in an application in
sequential order.
Now, you should define the validation points and expected results for each Test case which describe the
outcome of performing that Test case and criteria to determine if the Test case passes or fails.
The scenario parameters (variables) are hidden in the script.
Before continuing, let’s first take a look at the meaning of the following terms:
Action: An action can be thought of as the act of doing after a specific Test case occurred. The action
cares about the results and it will act based on its value.
In other words, an action specifies what happened after a Test case occurred and it is a part of the
Validation point.
Validation Point: A validation point verifies the outcome of the Test case. Usually a Test case has
several possible outcomes. For example, login might behave differently depending on whether the
username and password are correct, incorrect, too long, too short or just non-existent.
The action is the act of responsing and the validation point verifies the outcome when using valid,
invalid, too long, too short or just non-existent usernames and passwords.
Page 44
It is important to provide complete steps and expected results to avoid ambiguity during testing.
Choose a Test case and define an outcome name
Test case: Select the Test case you want to define an expexted result for it.
Outcome Name: A unique name used to identify the Test case result.
Action: There are 3 options that can be selected as an action:



Find Image
Desktop Screenshot
Component Cleanup
Page 45
1. When you choose “Find Image” action, a window will be popped up so that you can choose images.
Double-click on the image
to
Click to upload images

In order to upload a new image, click on the “Upload Image”
button. The “File Upload”
dialog box will appear over the active window. Select the desired image file, then click on open.
Select the picture and click on
“Open” to upload the image
Page 46
The picture will be added to the script images section.
Click to download the
screen capture tool
Remember only images with “BMP” format and less than 2 MB can be uploaded.

In order to take a screenshot, click on “Take ScreenShot”
“CaptureScreen”, the free screen capture, program.
After downloading the zip file
button to download the
, install the program and start using it.
Page 47
Once you double-click on the image, it will be automatically added to the “Action Value” textbox.
Next, click on
to add the action to the script.
You can view the selected image by clicking on the image action.
The “Add Action”
The “Add Validation Point”
button will be enabled once you select an action value.
button will be enabled once you have an action.
Page 48
2. When you choose “Desktop Screenshot” action, the value (Desktop Screenshot) will be automatically added
to the “Action Value” textbox.
Next, click on
3. You can choose “Component Cleanup” action if an available component does exist in the script.
Select your component from the drop down list to be added to the Action Value.
Page 49
Next, click on

To reset any action, click on “Reset Action”
button.
We recommend you to choose the “Component Cleanup” action as the last action.
You can add many actions for each Test case but only one validation point.
After adding the actions, click on “Add Validation Point”
button.
Once you click on it, the Validation point will be added to the top of the script.
Page 50
Validation point
Validation points can be inserted anywhere in the script, simply drag and drop them to the desired position.
Page 51
Use drag & drop to set
the Validation point
The validation points can also be added inside the sub-scenarios or components.
Validation Points for
different Test cases
Page 52
Sometimes the validation point cannot be dropped in the position for the following reasons:
1. The script you are using was created with ScenarioBuilder version < 8.1
2. The script was initially created with ScenarioBuilder version < 8.1 then it was modified by
ScenarioBuilder version >= 8.1
Invalid position means that the validation point is dropped after an element with id="0". One way to avoid this,
if your script is not created with ScenarioBuilder version >= 8.1, is to click on elements and check the attribute
id.

To edit the Validation point, click on it to make it selected.
Page 53
Once it is selected, you can edit the fields of the validation point in the left side of the section.

To delete the Validation point, click on it make it selected. Then click on
button.
When Test Plan Run is generated, all Test cases, scripts, scenarios steps, expected results, images, and
attachments will automatically be included in the Test Plan Run.
Page 54
Publish
When you are done with defining expected results and adding validation points to the Test Plan, click “Publish”
to complete the Test Plan.
Click to publish the Test Plan
Page 55
Once you click on the button, you will be automatically moved to the Manage Test Plans page.
Now the Test Plan is ready to be executed.
If you have not published a Test Plan, the Test Plan will be locked and it cannot be executed.
Any changes to the script (s), sub-scenarios, variables and other actions and resending them to the
Controller, requires you to publish the Test Plan again.
If you try to generate the Test Plan Run before publishing, a message pop up will be displayed to inform you to
publish the Test Plan again.
Page 56
After creating a Test Plan, you might want to review the Test Plan to check if all the Test cases cover the key
functionality of the application. To do this, click on button next to the Test Plan name to get an overview of
each Test Plan.
Group name and script’s name
Page 57
Generate Test Plan Run
Test Plan generating process consists of execution of all the Test cases in it. Test cases are executed one by one
according to their order in a Test Plan. To generate a Test Plan a new Test Plan Run, associated with the Test
Plan, should be created.
A new Test Plan Run will be created every time a Test Plan needs to be executed. This allows to track
summary of a Test Plan’s executions.
To start a Test Plan execution, click the “Generate Test Plan Run” button
next to the Test Plan.
Click to generate Test Plan Run
Once you click on it, you will be automatically forwarded to the Test Plan Run Report page.
Page 58
Click to play Test Plan Run
Add notes for Test Plan Run
Here you can see how many Test cases were created for a Test Plan Run and how many scripts have been added
to the Test Plan within each group..
Any changes except deleting, to a Test Plan after it has been moved to the Test Plan Run state are forbidden.




To delete the group, click on
button.
To delete the Test scenario, click on
To delete the Test case, click on
button.
button.
There is a Note section available on a Test Plan Run Report, so that you can type any notes about this Test
Plan Run if required.
Page 59
Before playing the Test Plan Run, make sure the rTester(s) is available. You can check the rTester status
from “View rTester” section. You can also check the availability of them by clicking on the
Menu Bar.
button in the
If you try to execute a Test Plan Run and there were not any rTester available, the AppVerify will display an
error message on the top of the Test Plan Run page.
Page 60
When you are done with the Test Plan Run, it is ready to be played. To do it, click on
button.
Here are some screenshots of the running process:
Test Run execution is in progress
Test case is playing
Click to stop the Test Plan Run
Test case is waiting to be played
Page 61
You can track the rTester’s status by checking the messages displayed on top of the page.
You can invisible them by unchecking the “Show rTester status”
option.
At any moment you can stop the test plan execution process. To do it, click on
button.
For every Test case AppVerify will specify its run result: Succeed , Failed or Not Played.

Succeed: The Test case has been passed successfully.

Failed: There are some issues related to this Test case.

Not Played: The Test Plan Run has been stopped and the Test case will be executed later.
Succeed
Failed
Not Played
After the Test Plan Run execution has been completed, the results will be visible on the Test Plan Run Report.
The report contains general information about the Test Run including the name of the Test Plan, Test Plan ID,
the number of the Test Plan Run, Test cases, error messages, screenshots, Run time and the test end time. It also
contains the optional note of the Test Plan Run that you add when you run the test.
At the top of the page you can see how many test cases have been Passed, Failed, or Not Played within a Test
Plan Run.
Page 62
The Test end time

To view the failure screenshot for the Failed ones, click on
(camera) button.
Page 63
After the Test Plan Run is over, AppVerify gathers various information on the Test Plan Run and shows this data
in the Test Plan Run Report. You can export this data to an external file to view it outside of AppVerify
Controller.

To export the report, click on “Export to Word”
specified .doc file.
button. AppVerify will export Test results to the
Click to export the report
Page 64
View Test Plan Run report
When a Test Plan Run has been executed, you can find its results in several different places throughout
AppVerify Controller.
To look your Test Plan last run results go to the Manage Test Plans page and click on “View Test Plan Run
Report”
button next to the Test Plan name.
Click to view Test Plan Run report
Once you click on it, you will be automatically moved to that Test Plan Reports page.
Click to view the Test Plan Run report
Page 65
Here you will see all the Test Runs executed for this Test Plan with its run results. It will show how many test
cases have been succeed, failed, or not played in every Test Run and allow to compare the results.
View the Test Plan Run report by clicking the
button next to the Test Run.
The Test Plan name, TestPlan ID and status (success, failure, not played) are displayed at the top of the page.
The other parts of the report contain detailed information on the Test Plan Run.
Page 66
Edit Test Plan
Edit a Test Plan by clicking the “Edit a Test Plan” button
Click to edit Test Plan
When you are done editing, you can click on “Publish” to make the Test Plan ready for execution.
Page 67
Delete Test Plan
Delete a Test Plan by clicking the “Delete this Test Plan” button
Click to delete Test Plan
Click on “Delete”
button to finalize the deletion of the Test Plan.
Page 68
Manage reports
When a Test Plan Run has been executed, results are posted to the Test Plan Run
report. You can find all reports through the Manage Reports section.
To open the “Manage Reports” page, simply click the “Manage Reports” button in the left pane of the AppVerify.
The “Manage Reports” page contains a list of all the Test Plan Runs. The name of the Test Plan, the Test Plan ID,
the project name, the scripts, the number of times it ran, and the date of the Test Run are displayed.
Start typing to find a Test Plan Run
Click to view all reports of the Test Plan Run

Use the filter
to search a Test Plan Run by Test Plan Run name.
You can choose a Test Plan Run to view all reports of that Test Plan Run and inspect more details about it. In
order to view all reports of each specific Test Plan Run, click on
button.
Once you click on it, you will be automatically moved to that Test Plan Reports page.
Please refer o the View Test Plan Run report section for more information.
Page 69
Latest Test Plan Run report
View the latest Test Plan Run Report by clicking the
button next to the Test Run. (i.e Test Run #10)
Click to view the latest Test Plan Run report
Click to delete the Test Plan Run
Page 70
Here you will see some details and the results of that specific Test Plan Run (i.e Test Run #10). It will show how
many Test cases have been succeed, failed, or not played in that Test Plan Run.
Click to delete the Test Plan Run

To delete the Test Plan Run, click on
button.
button to finalize the deletion of the Test Plan Run.
Page 71

You can filter the Test status on the Test Plan Run Report to create a new Test Plan Run more quickly. To do
this, click on
Check to filter
Here you can check each option to be included in the new Test Plan Run.
Next, click on “Submit”
button to complete the new Test Plan Run creation.
Here you will be able to play a new Test Plan Run based on the filter condition.
Click to play the Test Plan Run

To disable the filter, simply uncheck it on the “Filter Action” window.
Page 72
Test Plan Run summary report
The Test Plan Run summary report provides the key results in compact and easy to compare the results quickly.
Click to view the Test Plan Run summary report
View the Test Plan Run summary Report by clicking the
Page 73
Here you will see all the Test cases status for this Test Plan with their latest run results and Test Run numbers.

To reset the Test Plan Run summary, click on
button.
Click on “Reset”
button to complete the reset process.
If a Test Plan is in the “draft” mode, you are not allowed to reset the summary report of that Test Plan.
Page 74
View rTesters
This section provides you an option to view and manage different rTesters.
To open the “View rTesters” page, simply click the “View rTesters” button in the left
pane of the AppVerify. Here you can see some information about different rTesters.
rTester is busy, it cannot be deleted
Upon installation, a rTester will register itself with the AppVerify Controller. To view currently registered
rTesters, click on the “View rTesters” section in the “Left Pane”.
rTesters can only be added to the AppVerify Controller during the installation process.
rTesters can have 4 statuses: 1. Online
2. Busy
3. Reserved
4. Offline

To make the rTester to be reserved
, click on the desired rTester’s status button.

To delete the rTester, click on
button.
Page 75

button to finalize the deletion of the rTester.
To edit the rTester, click on
button.
After modifying the rTester details, click on “Update”

To close the form, click on “Close”
button to apply the changes.
button.
Page 76
Manage projects
The Manage Projects section lists all your projects. It also lets you to open and
close projects and manage existing ones. Under each project you can see the
project scripts / sub-scenarios.
To open the “Manage Projects” page, simply click the “Manage Projects” button in the left pane of the AppVerify.
Here you can see the “Projects List”.
Start typing to find a project

Use the filter

Close the project by clicking on the project’s status
to search a project by project name.
button.
Click on “Close Project”

button to close the project.
Open the project by clicking on the project’s status
button.
Page 77
Manage users
The AppVerify Manage Users section includes options that let you to create
and manage users and groups.
Users
When you log in for the first time, there is only one user account in the system, and
it is your account. You are an Administrator on default. Here you can manage the
users.
Create Users to control access to Projects, Test Plans and Reports. Users belonging to any group have selected
access based on the limitations of their group.
To open the “Users” page, simply expand the “Manage Users” section from the left pane of the AppVerify and
click the “Users” button.
Here you can see the “Users List”.
Go to Users section and click on
+
Page 78
Create new user
Click “Create New User” button
next to the “Users List” text. “Users Form” appears;
First Name: Specify the first name of the user.
Last Name: Specify the last name of the user.
Username: Specify a unique username for this user. Usernames must begin with an alpha character and are
case-sensitive.
Email Address: Provide the email address for this user.
Password: Enter a password for this user. Passwords are case-sensitive.
Confirm Password: Re-enter the password.
Check the “Administrator” box if the user shall have full administrative rights for the entire application.
After you put all the fields, click on “Submit”
button to create the user.
Page 79
Once you create the new user, it will be added to the “Users List”.

The Users Form can be closed by clicking on

The form can be reset by clicking on “Reset”
button.
button.
Edit user
Edit a user by clicking the “Edit User information” button
next to the user.
Delete user
Delete a user by clicking the “Delete this User” button
next to the user.
If a Test Plan is locked by a user and the user has been deleted, the Test Plan will be unlocked.
Page 80
Groups
Create Groups to control access to Projects, Test Plans and Reports. Users
belonging to any group have selected access based on the limitations of their
group.
To open the “Groups” page, simply expand the “Manage Users” section from the
left pane of the AppVerify and click the “Groups” button.
Here you can access to the “Groups List”.
Go to Groups section and click on
+
Create new group
Click “Create New Group” button
next to the “Groups List” text. “Groups Form” appears;
Name: Specify the name of the group.
Description: Enter an optional description to help identify this group.
Page 81
Users List: Select a user to assign the project. You can choose multiple groups. You might need to scroll down to
find the user in the list.
Selected Users: The selected users will automatically appear here.
Click “Submit”
to create the group.
Once you create the new group, it will be added to the “Groups List”.

The Groups Form can be closed by clicking on

button.
button.
Edit group
Edit a Group by clicking the “Edit Group information” button
next to the Group.
Delete group
Delete a Group by clicking the “Delete this Group” button
next to the Group.
Page 82
User profile
A user profile is the collection of user information and preferences—and the settings associated with
each of those preferences —that describe a single user. To view the user profile, click on the user image on the
Left pane.
Once you click on it, the profile of that user will be displayed.
Click to view user profile
Your AppVerify user profile shows your personal details registered in AppVerify and your AppVerify
preferences such as pagination page size, the number of Test Runs per report, etc.
Page 83
User information
The User Information is where you specify your personal settings (e.g. your email address, password, user’s
image).
First Name: Specify the first name of the user.
Last Name: Specify the last name of the user.
Username: Specify a unique username for this user. Usernames must begin with an alpha character and are
case-sensitive.
Email address: Provide the email address for this user.
Password: Enter a password for this user. Passwords are case-sensitive.
Change password:
You can change your password within the user information of your profile.
First, click on “Change Password”
button and enter your current password.
Click to change password
Page 84
Next, enter the new password you would like to change it to in the "New Password" box, then again into the
"Confirm Password " box to confirm.
After your are done with the editing, you have to put your password to be able to save the changes. Once you
start typing your password, “Save Changes”
Now, click on “Save Changes”
button will be enabled.
button to record your changes.
When you navigate to any other page and during any other future login, you will need to use your new
password you set.

In order to cancel the Change Password option, click on “Cancel”
Password” text.
button next to the “New
Page 85

In order to change the user’s image click on the “Upload Image”
button.
The “File Upload” dialog box will appear over the active window. Select the desired image file, the click on
open.
Select the picture and click on
“Open” to upload the image
The picture will appear in the image area.
Don't forget to enter your password to save the changes.
Page 86
User preferences
In the User Preferences section on the User Profile page, you can edit the following options:
Pagination Page Size (5 to 30): The number of items displayed on each page. The default value is 10.
Number of Test Runs per report (5 to 20): The number of Test Run reports displayed on the report page. The
default value is 10.
Test Plan Run Refresh Interval (5 to 60 seconds): The Test Plan Run Refresh Interval is an amount of time
between 5 and 60 seconds, which is used to determine when the Test Plan Run status should be updated. The
default value is 10.
rTester List Refresh Interval (10 to 120 seconds): The rTesters List Refresh Interval is an amount of time
between 10 and 120 seconds, which is used to determine when the rTseters list should be updated. The default
value is 20.
Number of rTester Messages in Test Plan Run (1 to 5): The number of rTester’s messages displayed on the
Test Plan Run page. The default value is 5.
Page 87
After your are done with the editing, you have to put your password to be able to save the changes. Once you
start typing your password, “Save Changes”
Now, click on “Save Changes”
button will be enabled.
button to record your changes.
The following message will appear:
Page 88
Settings
The AppVerify Settings section includes options that let you define default ID for
your Test Plans and set the Initializing Script Delay.
Test Plan Options
You can set the following options for the Test Plan:
ID Prefix: Specify a name for the Test Plan. The default name is : ATP (AppVerify Test Plan)
Test Plan ID is just a unique number/name for future reference.
ID Suffix Length: Choose the ID length [4-15]. This will create a unique number. The default value is 5.
Preview: This is how the Test Plan ID will be displayed.
Initializing Script Delay: The time, in seconds, that each rTester waits before playing the Initializing Script. A
Delay value of "0" results in all rTesters begin playing the Initializing Script simultaneously. A Delay value of "5"
results in each rTester begin playing the Initializing Script 5 seconds after the previous. The default value is 15
seconds.
Click “Update”
to update the changes.
Page 89

button.
Page 90
Appendix
API specification
Methods
1. Generate Token
Authenticate the user with AppVerify, and obtain a token.
Request
Method
URL
POST
/api/generatetoken/
Type
Params
Values
HEAD
POST
POST
Accept [optional]
Username
password
String
String
String
Accept:
This header is optional and it can take one of the following values:


application/xml
application/json
The default value is: application/xml
Request Example using cURL:
Curl -X POST
application/json"]
-d
"username=[username]&password=[password]"
http://10.0.0.48:8888/api/generatetoken
[-H
"Accept:
Page 91
Response
Status
200
401
400
400
500
XML Response (default)
JSON Response
<?xml version="1.1" encoding="utf-8"?>
<root>
<token>
[TOKEN VALUE]
</token>
</root>
<root>
<non_field_errors>
<list-item>
Unable to log in with provided
credentials.
</list-item>
</non_field_errors>
</root>
<root>
<password>
<list-item>
This field is required.
</list-item>
</password>
</root>
<root>
<username>
<list-item>
This field is required.
</list-item>
</username>
</root>
{"token": "[TOKEN VALUE]"}
{
"non_field_errors":
["Unable to log in with provided credentials."]
}
{
"username": ["This field is required."]
}
{
"password":
["This field is required."]
}
AppVerify ServerError 500!
Page 92
2. Generate a Test Plan Run
This method generate a Test Plan Run based on an existing Test Plan. It takes the Test Plan ID as input. If
the Test Plan Run was created successfully, it will send the Test Plan Run Number back.
Request
Method
URL
POST
/api/createtpr/
Type
Params
Values
HEAD
HEAD
POST
Accept [optional]
Authorization
tp_id
String
String
String
Accept:


application/xml
application/json
Authorization:
This header should include the token value to authenticate the request.
Example:
Authorization: Token [Token Value]
tp_id:
This parameter will be the Test Plan ID that you want to create a Test Plan Run for.
Example:
tp_id=ATP-96974
Page 93
Curl -X POST http://10.0.0.48:8888/api/createtpr -H "Authorization: Token [Token Value]" -d "tp_id=[Test Plan ID]" [-H "Accept:
application/json"]
Response
Status
200
400
401
500
JSON Response
<root>
<success>
Test Plan Run was created successfully
</success>
<tpr_id>
[Integer]
</tpr_id>
</root>
<root>
<fail>Test Plan Run was not created</fail>
</root>
<root>
<detail>Invalid token</detail>
</root>
{
"tpr_id": [Integer],
"success":
"Test Plan Run was created successfully"
}
{"fail": "Test Plan Run was not created"}
{"detail": "Invalid token"}
Page 94
3. Play a Test Plan Run
This method finds the available rTesters and have them start playing the scenarios in a specific Test Plan
Run.
Request
Method
URL
POST
/api/playtpr/
Type
Params
Values
HEAD
HEAD
POST
POST
Accept [optional]
Authorization
tp_id
tpr_id
String
String
String
Integer
Accept:


application/xml
application/json
Authorization:
Example:
Authorization: Token 1971df76756663e9b90b28811bf6dd8b6aab4e0abf9f
tp_id:
Example:
tp_id=ATP-96974
Page 95
tpr_id:
This parameter will be the Test Plan Run number that you want to be played on the rTester(s).
Example:
tpr_id=5
curl -X POST http://localhost/api/playtpr -H "Authorization: Token [Token Value]" -d "tp_id=[Test Plan ID]&tpr_id=[Test Plan Run #]" [-H
"Accept: application/json"]
Response
Status
200
400
400
400
401
500
JSON Response
<root>
<success>
Test Plan Run started to play
</success>
</root>
<root>
<fail>
Test Plan Run was already played
</fail>
</root>
<root>
<fail>
Test Plan Run Number 0 cannot be played
</fail>
</root>
<root>
<fail>
No available rTesters found
</fail>
</root>
<root>
<detail>
Invalid token
</detail>
</root>
{"success": "Test Plan Run started to play"}
{"fail": "Test Plan Run was already played"}
{"fail": "Test Plan Run Number 0 cannot be played"}
{"fail": "No available rTesters found"}
Page 96
4. Generate and play a Test Plan Run
This method generate a Test Plan Run based on an existing Test Plan. It takes the Test Plan ID as input. Then, it
finds the available rTesters and have them start playing the scenarios in a specific Test Plan Run.
Request
Method
URL
POST
/api/createandplaytpr/
Type
Params
Values
HEAD
HEAD
POST
Accept [optional]
Authorization
tp_id
String
String
String
Accept:


application/xml
application/json
Authorization:
Example:
Authorization: Token [Token Value]
tp_id:
Example:
tp_id=ATP-42324
Page 97
Curl -X POST http://10.0.0.48:8888/api/createandplaytpr -H "Authorization: Token [Token Value]" -d "tp_id=[Test Plan ID]" [-H "Accept:
application/json"]
Response
Status
200
400
400
401
500
JSON Response
<root>
<success>
Test Plan Run was created and started to play
</success>
<tpr_id>
[Integer]
</tpr_id>
</root>
<root>
<fail>Test Plan Run was not created</fail>
</root>
<root>
<fail>No available rTesters found</fail>
</root>
<root>
<detail>Invalid token</detail>
</root>
{
"tpr_id": [Integer],
"success":
"Test Plan Run was created and started to play"
}
{"fail": "Test Plan Run was not created"}
{"fail": "No available rTesters found"}
Page 98
Glossary
Conventions
●
●
●
●
●
Status - HTTP status code of response.
All the possible responses are listed under ‘Responses’ for each method. Only one of them is issued per
request server.
All response are in XML format. Unless the Accept header was set to application/json
All request parameters are mandatory unless explicitly marked as [optional]
The type of values accepted for a request parameter is shown the values column like this. The | symbol
means OR. If the parameter is [optional].
Status codes
All status codes are standard HTTP status codes. The below ones are used in this API.
2XX - Success of some kind
4XX - Error occurred in client’s part
5XX - Error occurred in server’s part
Status Code
Description
200
OK
400
Error in the request
401
Authentication failure
500
Internal Server Error
Page 99
Getting help
Free POC!
Need a Proof of Concept? Our experts will help establish AppVerify’s viability so that your
organization, from stakeholders down to data entry clerks, is 100% behind your decision to go
forward with AppVerify!
If at any point during your trial you need more help, our technicians are waiting to help you!
Don’t hesitate to call our experts at 888-624-4447 or email NRG Global Support
[email protected].
You can also ask questions, search for answers, exchange comments and suggestions on our
Testing Community, find answers to your questions in the list of the Frequently Asked
Questions, watch Training Videos and take part in NRG Global training services.
Page 100
Index
A
Action .................................................................................................... 46
Action Value ....................................................................................... 48
Alerts ..................................................................................................... 29
AppVerify ............................................................................................... 4
AppVerify Controller ...................................................................... 23
B
Build Test Plan .................................................................................. 36
Busy rTester ....................................................................................... 72
C
Change password ............................................................................. 81
Component Cleanup ....................................................................... 47
Create new Test Plan ...................................................................... 36
D
Dashboard ........................................................................................... 31
Dashboard ................................................................................... 28, 29
Data ........................................................................................................ 40
Desktop Screenshot ........................................................................ 47
Draft ....................................................................................................... 34
E
Expected Outcome ........................................................................... 46
M
Manage projects ................................................................................74
Manage reports .................................................................................66
Manage Test Plans ...........................................................................34
Manage users .....................................................................................75
Menu Bar ..............................................................................................29
N
Not Played ...........................................................................................59
Note ........................................................................................................56
Number of rTester Messages in Test Plan ............................84
Number of Test Runs per report ...............................................84
O
Offline rTester ...................................................................................72
Online rTester ....................................................................................72
Outcome Name ..................................................................................47
P
Pagination Page Size .......................................................................84
Plan .........................................................................................................37
Project ...................................................................................................37
Project Script ......................................................................................39
Publish ..................................................................................................54
R
F
Failed ..................................................................................................... 59
Filter ...................................................................................................... 68
Find Image .......................................................................................... 47
G
Generate Test Plan .......................................................................... 55
Groups ........................................................................................... 37, 78
H
Help ........................................................................................................ 29
L
Left Pane .............................................................................................. 29
Locked Test Plan .............................................................................. 34
Log out .................................................................................................. 29
Reference time ..................................................................................25
Regression testing ............................................................................. 4
Reserved rTester ..............................................................................72
rTester ..................................................................................................23
rTester List Refresh Interval .......................................................84
S
Scenario parameters .......................................................................40
ScenarioBuilder ................................................................................23
Scripts....................................................................................................39
Settings .................................................................................................85
SMTP configuration.........................................................................86
SSrdpManager ...................................................................................24
Stop on error .............................................................................. 38, 44
Succeed .................................................................................................59
Support .................................................................................................29
Page 101
T
Test case ...................................23, 31, 40, 43, 46, 47, 54, 56, 59
Test cases ............................................................................................. 43
Test Plan2, 3, 4, 23, 34, 35, 36, 37, 38, 41, 43, 44, 45, 53,
54, 55, 56, 57, 59, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70,
71, 84, 85, 86
Test Plan ID ......................................................................................... 85
Test Plan Run ..................................................................................... 23
Test Plan Run Refresh Interval .................................................. 84
Test Plan Run Report ..................................................................... 59
Test Plan Run summary report ................................................. 70
Test scenario ....................................................................... 23, 46, 56
Test variables ..................................................................................... 40
User preferences ..............................................................................84
User profile .........................................................................................80
Users ......................................................................................................75
V
Validation Point ................................................................................46
Variable Name ...................................................................................40
Variable State .....................................................................................40
Variable Value....................................................................................40
View rTesters .....................................................................................72
View Test Plan Run report ...........................................................62
W
Word document file ................................................................ 61
U
User information .............................................................................. 81
Page 102

AppVerify 1.1

Transcription

Similar documents

Llanelli Rural Council Swiss Valley Design Proposal 2 1 4 5 6 2 3 8

Flatbed

AppVerify 1.1

MSC Report_CUIDEMOS Mexico

Hotmail/Live/ MSN/Outlook.com

parents! - First In Math

- Saurashtra University

Go to Website highereduhry.com Click on online admission button

Time Sheet Reminder

Disney Princess Magic Wand Laptop

Form 10-K - Investor Relations Solutions