Inspecting an Application Blueprint Model in Test Modeller

Search Knowledge Base by Keyword

< Back

Application Blueprints are models of the logic recorded across all journeys in a session.

The flowchart models are directed graphs that visually represent the cause and effect logic of the recorded activity. They are made up of:

  1. Processes: the blocks in the flowchart model. These can be either actions or events. Actions exercised by the manual tester or automated test are represented by yellow blocks. Events such as URL changes are represented by red blocks.
  2. Outputs and edges: The arrows connecting the blocks. These represent transitions in the system logic.

VIP Test Modeller Explorer_The UI Recorder_Inspecting a Model_1

A linear journey or “path” through a model is equivalent to a set of “If … then …” statements that reflect a singular recorded journey through the application logic. Decisions occur when a given process block has multiple edges. The model then collates collectively all recorded journeys, with the overlapping test steps consolidated in visual form.

The models serve as an accelerator to test case generation using Test Modeller. They are mathematically precise and can therefore be imported to new or existing models in the Test Modeller workspace.

You can then build additional logic around the recorded activity, before applying the automated test case generation algorithms to generate an optimised set of test cases from the recorded activity. The generated tests will, at a minimum, cover the same logic as the recorded tests, but in potentially fewer tests; however, the recorded activity also provides a starting point to begin creating a more comprehensive set of tests, optimised based on time and risk factors.

Journey Overview Models

The default Application Blueprint models are the highest level, displaying the interrelations between pages in the recorded activity.

To view an overview model, log-in to Test Modeller and select the context that corresponds to the relevant recorded journeys. Next, navigate to the “Blueprint” tab, under “Test Insight” in the sidebar. The overview model will display the relationship between individual pages exercised in the recorded activity. Each page is represented by a silver block:

VIP Test Modeller Explorer_The UI Recorder_Inspecting a Model_2

Clicking the plus for a given page will display the logical model of activity executed against that page:

VIP Test Modeller Explorer_The UI Recorder_Inspecting a Model_3

You can also select “Expand All” and “Collapse All” to display all or no page activity in an overview model.

The models are interactive. Process blocks and page blocks can be arranged by clicking and dragging them. Clicking a process block or arrow will also display the information recorded during that activity. The “Attributes” tab displays the recorded interaction activity for a selected block or arrow:

VIP Test Modeller Explorer_The UI Recorder_Inspecting a Model_4

The “Data” tab allows you to inspect the data associated with given user interactions. To view the data, select a yellow interaction block, and navigate to the data tab. Next, select the “Data Matrix” option. This will display the data entered into a given element:

VIP Test Modeller Explorer_The UI Recorder_Inspecting a Model_5

In the above example, a user selected the “User Name” element on a form, and typed “tom” and the tab key. This was part of a journey recorded under the name “Valid log-in”.

The “Image” tab displays a screenshot of the page at the time of the interaction, and an image of the element being interacted with.

An Application Blueprint displays the logic that has been recorded across all journeys executed against a given page. The “Journeys” tab displays the journeys that have exercised the selected block or edge. A link is provided to the journey entry in the workspace. The “Highlight All” button will highlight the entire journey that a given block features in, with every edge involved in those journeys in red:

VIP Test Modeller Explorer_The UI Recorder_Inspecting a Model_6

Below the model browser, information is provided for each interaction and event contained in a model. Scroll down to view the recorded description, the object ID, interaction type, and any test data values entered:

VIP Test Modeller Explorer_The UI Recorder_Inspecting a Model_6b

Page Models

You can also build an Application Blueprint model for an individual page that has been recorded. In Test Modeller, navigate to the “Blueprint” tab in the side bar, and then select “By Page”. This will open a pop up with a drop-down menu of all recorded pages associated with the selected context:

VIP Test Modeller Explorer_The UI Recorder_Inspecting a Model_7

Choose the relevant URL and click “Create”. This will generate an Application Blueprint for the individual page, that contains all the same information as an overview model, and can be browsed in the same way:

VIP Test Modeller Explorer_The UI Recorder_Inspecting a Model_8

User Activity Models

Application Blueprint models can likewise be built for all the activity recorded by a given user. Navigate to the “Blueprint” tab in the side bar, and then select “By User”. This will open a pop up with a drop-down menu of email addresses associated with each user associated with the workspace you are working in:

VIP Test Modeller Explorer_The UI Recorder_Inspecting a Model_9

Choose the relevant user and click “Create”. This will generate an overview model for all activity recorded using the selected email to log-in to the Test Modeller Explorer plug-in for Chrome.

Build Models from Custom Parameters

You can also build models from custom parameters, for instance generating models that reflect a particular user’s activity on a certain page.

Navigate to the “Blueprint” tab in the side bar, and then select “Custom”. This will open the filters panel: 

Models can be built based on the page, user, project, release, session, and source. To add a filter, select “AND” or “OR” from the drop-down menu and click “Add Condition”. Next, select the filter category and type of filter from the drop-downs. Finally, specify the page URL, user email, etc. from the third drop-down.

Click “Apply” once you have finished adding filters. Scroll down to see your generated model.