To create a new Test Plan, go to "Manage Test Plans" section and click on “Create New Test Plan” button next to the “Test Plans List” text.
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:
Test Plan: A unique name used to identify this Test Plan. (Use standard alpha/numeric characters only.)
Note: 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.
Tip: 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 button.
Next, click on button next to the desired group to continue.
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.
Note: Do not confuse this option with the “Stop on error” option for the scripts. For more information, see Test cases section.
Note: 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:
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 button.
Next, click on button next to the desired script to continue.
Note: AppVerify gives you the option to to change the order of Test Plan scripts in a group by clicking on Up/Down icons.
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].
Note: Do not remove the beginning and ending brackets from the pre-defined values; multiple modification (addition, subtraction) are allowed per variable value.
- To add the variable to the Test Plan, Click on button.
Note: The variables can have empty values. Once you put empty value in the “Variable Value” textbox, it will be displayed as “empty value”.
- To edit each variable select and edit the variable and then click on button to apply the changes.
- To delete the variable click on button.
- To reset the changes, click on button.
Note: You are not allowed to delete the Variable state for the Default Test case but you can modify the variable value.
Note: If you try to create duplicate vraibale states, AppVerify will overwrite the variable value.
- To export variables click on button. AppVerify will export script variables to the specified .xls 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.
Once you import the correct file, you will see the new data.
Warning: 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.
Once you click on it, a message pop up will be displayed;
To generate new Test cases, click on “Generate” button.
Note: Click on “View Existing Test cases” button to see the previous 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.
- To edit the Test case, click on each variable you want to modify and make the changes.
- To delete the Test case, click on button.
- To create a new Test caseand add it to this Test Plan, click on button.
Enter the details for your new Test case including the variables and the values.
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.
When all the Test cases in a Test Plan have been generated, the Test Plan can be moved to its final step.
Next, click on button.
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.
Note: The scenario parameters (variables) are hidden in the script.
Tip: 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 responding and the validation point verifies the outcome when using valid, invalid, too long, too short or just non-existent usernames and passwords.
Note: It is important to provide complete steps and expected results to avoid ambiguity during testing.
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
1. When you choose “Find Image” action, a window will be popped up so that you can choose 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.
The picture will be added to the script images section.
Note: Remember only images with “BMP” format and less than 2 MB can be uploaded.
- In order to take a screenshot, click on “Take ScreenShot” button to download the “CaptureScreen”, the free screen capture, program.
After downloading the zip file , install the program and start using it.
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.
Tip: You can view the selected image by clicking on the image action.
Note: The “Add Action” button will be enabled once you select an action value.
Note: The “Add Validation Point” button will be enabled once you have an action.
2. When you choose “Desktop Screenshot” action, the value (Desktop Screenshot) will be automatically added to the “Action Value” textbox.
Next, click on to add the action to the script.
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.
Next, click on to add the action to the script.
- To reset any action, click on “Reset Action” button.
Tip: We recommend you to choose the “Component Cleanup” action as the last action.
Note: 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.
Validation points can be inserted anywhere in the script, simply drag and drop them to the desired position.
Tip: The validation points can also be added inside the sub-scenarios or components.
Warning: Sometimes the validation point cannot be dropped in the position for the following reasons:
- The script you are using was created with ScenarioBuilder version < 8.1
- 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.
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.
Note: 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.
When you are done with defining expected results and adding validation points to the Test Plan, click “Publish” to complete the Test Plan.
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.
Note: If you have not published a Test Plan, the Test Plan will be locked and it cannot be executed.
Note: 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.
Tip: 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.