Recording a Journey
Search Knowledge Base by Keyword
The UI Recorder captures activity that is executed against a web UI, either by a manual tester of automated test.
The UI Recorder records “Journeys” through a UI, that are equivalent to tests. The recordings contain everything needed for automated testing: interactions with the application, the data entered, any message traffic generated, and the console activity. This information is stored and modelled in Test Modeller, where it can be analysed or overlaid onto logical models of the system under test. This allows you to automatically generate an optimised set of automated tests from the model.
Journeys are recorded as part of a “Session” that is then uploaded to a given “Context” in Test Modeller. This enables you to easily roll-back to previous recordings stored in a given Context, repeating a set of interactions as automated tests.
Note: You should record each individual test as its own individual Session, and each Session should be uploaded individually to Test Modeller. This reduces the amount of model editing required later. The process is as follows:
- Record an individual test as a Session.
- Upload the Session to Test Modeller.
- Reset the UI Recorder.
- Record the next test.
- Upload the Session to Test Modeller.
- Once you have recorded every test, import the activity to models in Test Modeller.
To record a test, navigate to the web UI under test. Next, open the Test Modeller Explorer extension, log in, and select the relevant workspace, project, and release.
Click the “start” button in the main panel of the Test Modeller Explorer to begin recording the Session:
The Test Modeller Explorer icon will turn red to indicate that it is recording. To record activity once the recorder is running, simply execute the manual test as normal, or run the automated test or bot.
The UI Recorder will provide notifications of what is being recorded and how that interaction is being tagged:
When you have finished recording the test, navigate to the Test Modeller Explorer icon to open the menu. Click “Stop” and the recording will end. The Test Modeller Explorer will report the number of interactions recorded, and the recording time:
You can now review, edit and upload the Session. Once you have uploaded the session, click “Reset” before recording your next test.
Recording can also be paused in the Test Modeller Explorer menu. If you pause a recording and click “Start”, further activity will be recorded as part of the same session. If you stop a recording and click “Start”, a new session will be created and previous activity will be lost.
The “Reset” button also deletes recorded activity.
-
-
-
- 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
-
-