Viewing a Journey in Test Modeller
Search Knowledge Base by Keyword
Recorded journey sessions are accessible from the Test Modeller workspace.
To view journeys, log-in to Test Modeller and select the relevant context. Next, navigate to the “Journeys” tab, under Test Insight in the sidebar. This will display the recorded journeys in the workspace:
The “History” drop-down allows you to browse journeys at different points in the application history. The “Refresh” button will display any activity recorded while Test Modeller is open. Recorded Journeys can also be deleted using the delete button:
There are three views available for each journey:
Interaction Activity
Viewing interaction activity shows the actions recorded for a given journey, ordered by action.
The attributes tab allows you to edit information associated with a given activity, including the URL, the description, object type, and page object ID. The interaction type can be edited, as can the data value entered. The code snippet displays the automation code that can execute a recorded action. The following example shows the information captured when a user typed the username “tom” into a text box with Object ID “USER_NAME”:
The “State” tab displays the page state at the time of the interaction. It includes a copy of the page HTML, the Element HTML, the Element CSS, and any relevant and active cookies.
The “image” tab displays a screenshot of the moment when the action was recorded, and the “history” lets you browse the previous executions of the journey by date and time.
Message Activity
Viewing message activity shows the requests and responses intercepted during the most recent journey execution. It includes all the metadata needed for effective service and message virtualization, as well as for automated testing across distributed systems and APIs.
Click the message activity icon next to a journey in the workspace to open the message activity panel. Traffic is broken down by each request-response pair:
In the request tab, the message traffic column displays requests ordered by row. It provides a quick display of the request method and type, and the URL.
Clicking on a request allows you to view and edit the request data. This includes the request type, for instance “GET” or “POST”, as well as the request type, such as XMLHttpRequests (XHRs) or requests made to the mainframe. The URL can further be edited, as can the request header and body.
The response tab displays the corresponding response data:
This includes the URL, timestamp, type, method, the status code, status line, body, header, and whether or not the response came from Cache.
Console Activity
The console activity panel displays any JavaScript errors or warnings that occurred during the most recent journey execution:
The error exception and Javascript call-stack are displayed with each console message.
-
-
-
- IEnumerable to Data Reader
- Data Table to List
- Nested String List to Data Table
- List to Data Table
- IEnumerable to List
- List to IEnumerable
- Remove from List
- Exists in List
- Value Exists in Dictionary
- Key Exists in Dictionary
- Remove from Dictionary
- Get from Dictionary
- Clear Dictionary
- Add to Dictionary
- Clear List
- Add to List
- Show all articles ( 1 ) Collapse Articles
-
-
-
-
- Explanation of Remaining Sheets in the Control Spreadsheet (for reference only)
- The ForeignKeys Sheet - Specifying which Foreign Keys to read from the Source Database
- The Tables Sheet: Defining Metadata that will be read from the Source Database
- The ProcessModel sheet – Toggling Subset Rules
- Refining the Control Spreadsheet
- Overview of the Advanced Control Spreadsheet
- Introduction
-
- Drop both Primary and Foreign Keys (The composite DROPKEYS Action)
- Validate Both Primary and Foreign Keys (The composite ValidateKeys Action)
- Add Both Primary and Foreign Keys (The Composite ADDKEYS action)
- Drop Tables
- Truncate Data
- Delete Orphans
- Drop Primary Keys
- Drop Foreign Keys
- Validate that Foreign Keys are Unique
- Validate that Primary Keys are Unique
- Add Foreign Keys
- Add Primary Keys
- Overview of Post-Subset Actions
-
-
- Use Event Hooks to call VIP Flows
- Different Methods for Connecting to Source Databases
- PreProcess Variables and Parameters
- Using SQL Functions to query Databases and Using the Queries in Data Generation Functions
- Summary of the Process to Configure the Test Data Configuration sheet
- How the PreProcessVariables Table is used in the Configuration sheet
- Sample Commerce Configuration Sheet Examples
- Adding Event Hooks in Configuration sheet for custom functionality
- How to Configure the Synthetic Test Data Configuration Control Sheet
-
-
-
-
-
- The UI Recorder
- Test Modeller – Maintenance
- Test Modeller Core (Linux) Optional – Postgres LDAP
- Test Modeller Core (Linux) Optional – SSL Certificate Installation
- Test Modeller Core (Linux) Optional – Active Directory
- Test Modeller Core (Linux) Installation
- Test Modeller: Software Pre-requisites
- Test Modeller : Installation components
- Test Modeller : System requirements (Windows, Linux)
-
-
-
-
-
-
- Common Problems
- Extend Test Modeller (Advanced)
- Edit Code Templates (Advanced)
- Import existing framework / custom page objects (Advanced)
- Execute Tests (Java)
- Generate Automation Code
- Build a Model (Java)
- Scan an Existing Web App
- Configuration (Java)
- Prerequisites (Selenium Java)
- Welcome Selenium (Java)
-
-
-
-
- Generate Optimised Test Cases and Data into Excel
- Implement Naming Conventions
- Page Object Generation
- Intelligent Page Objects
- Customising Page Objects
- Import Custom Code Snippets
- Rule-Based Test Generation
- Trigger Automation Execution from within Test Modeller
- Automation Configuration
- Test Data Automation for Gherkin Specifications
-
-