Test Case Authoring– Mainframes
Author a test case to automate a Mainframes Application
This guide provides a detailed description of authoring a Test Case in Avo Assure to automate a mainframes application.
Note: For the ‘Mainframe’ application type, all automation is performed solely in the Test Case authoring phase. The scraping process is not required to automate a mainframes application in Avo Assure.
- 1.Click on a ‘Design task’ of the ‘Mainframe’ application type in the ‘My Task’ Pane on the Avo Assure landing page.
Landing Page – My Tasks Pane
2. The test case authoring page will be displayed for the ‘Mainframe’ application type.
Test Case Authoring Page
Note: The test step consists of below:
- 1.Object Name: All the objects present in the corresponding screen will be visible in this column.
- 2.Keyword: Keyword column provides a list of all the actions that can be performed on the object selected in the column.
- 3.Input: The input column provides a placeholder for the user to provide relevant input to the action being performed.
- 4.Output: The output column provides a placeholder for the user to obtain relevant output after the step has been executed.
3. Click on the step that has been created.
Select Test Step
Note: On selecting, the step color is changed.
4. Click on the ‘Edit’ icon to start the Test Case authoring.
Edit Test Case
Note: On click of Edit, ‘@Generic’ is displayed in the Object column and the ‘GetFromClipBoard’ keyword is displayed under the Keyword column by default.
5. Click on the dropdown in the ‘Object Name’ column to select the object on which the action needs to be performed.
6. On the selection of a particular object, the corresponding keywords are populated.
7. Add the corresponding ‘Input and Output’ values, if required, and press ‘Enter’ on the keyboard.
8. To add more steps, click on the ‘Add test step’ icon.
Add Test Step
9. Click on the ‘Save’ button to save the Test Case, once all the steps are added.
Save Test Case
- 1.Click on the ‘Mainframe’ icon from the Action Bar under the ‘Debug On’ options to debug the Test Case.
Debug Test Case
Note: Use the ‘Add Dependent Test Cases’ option if other Test Cases have to be debugged before the current Test Case.
2. On completion of debugging, the ‘Debug completed successfully’ message is displayed.