Auto Prudent Support

After you define your requirements, you need to determine your testing goals. To do this, examine your application, system environment, and testing process to outline the testing strategy for achieving your goals.

 After you determine your testing goals, you build a test plan tree, which hierarchically divides your application into testing modules, or subjects. For each subject in the test plan tree, you define tests that contain test steps.

 For each test step, you specify the commands to be performed on your application. You can increase the flexibility of a test step by adding parameters.

 To keep track of the relationship between your tests and your requirements, you can add links between them. This can help you ensure compliance with your requirements throughout the testing process.

1. Creating Test Case Tree

The typical application is too large to test as a whole. The Test Plan module enables you to divide your application according to functionality. You divide your application into modules, or sub modules, by creating a test plan tree.

The test plan tree is a graphical representation of your test plan, displaying your tests according to the hierarchical relationship of their functions. After you define modules in the tree, you decide which tests to create for each modules, and add them to the tree.

2. Display Test Plan Tree

Click the Test Plan Folder Icon in the tool bar.

3. Click Create New Test Plan Icon

4. Add details to the Test Plan – Overview Tab

5. Map the Test Cases to Requirements

Designing Test Steps

After you add a test to the test plan tree and define basic test information, you define test steps—detailed, step-by-step instructions that specify how your steps execute the test. A step includes the commands to be performed on your application and the parameters.

1. Double click on the Test Command cell, a dropdown will be displayed with list of mobile commands.

Auto Prudent Test simplifies the development of test cases allowing users to select commands during test development phase. Commands in Auto Prudent Test perform operations on the required objects (UI controls) as per their predefined command. Commands are associated with different objects of the application under test.

2. Usually, multiple commands are mapped with required object in the application to allow users to perform different operations on the object. However, some commands do not have objects associated with them. For example, the MobiTypeTextinTextBox sets a value in specific Edit box control.

The following example explains the usage of commands.

• A typical login screen on a mobile application may have two text boxes for entering user name and password. These text boxes are the controls or the objects in an application. 

• The login screen also has a Submit button, which is also an object, to log on to the application. The command for the user name text box is MobiTypeTextinTextBox. 

• This command enters a value into an edit box. The string value in the edit box is the single input (parameter) for this command. The command for the Submit button is ClickMobiButton. 

• This command performs a click operation on the Submit or Sign In button. No parameter is required for this command.

So the test steps for the above example would be like this.

3. Once you created the test steps, click on Submit Button, to get the steps saved.

Test Commands

Test commands are classified as

• Common Mobile Commands 

• Specific Mobile Commands