Execute
Create end to end tests on our test editor page
The Execute feature in Revyl allows you to create and manage end-to-end tests directly from the test editor page. Here’s a guide on how to use this feature effectively:
Managing Devices
Starting a Device
To begin testing, a cloud device must be started. This can be done by clicking the “Start Device” button in the test editor. This action initializes a virtual device where tests can be executed. Viewport size can be adjusted through the dropdown menu.
Already Running Devices
Once testing is complete, or if you need to halt the testing process for any reason, you can stop the cloud device by clicking the “Stop Device” button. This helps in managing resources and costs effectively.
Restarting a device will stop the current device and start a new one, useful for clearing cookies and starting fresh.
Check Pages will force check for other pages that are open on the device.
Creating Test Steps
- Types of Steps: You can create various types of steps in your test, such as clicking buttons, entering text, or navigating through the application. Each step can be defined using simple commands or by recording actions directly on the cloud device.
Broad Steps Types
Instruction - Natural language instruction such as Sign-in
- step (str)
Validation - Natural language validation to test if a condition is true. A validation could be something like Confirm that the user is on the checkout page
- validation (str)
Extract - Parse data from the current state into a json structure
- extraction (str)
Manual Actions
Navigate - Navigate to a specific url
- (str) url to navigate to
Back - Go back to the previous page
Forward - Go forward to the next page
Refresh - Refresh the current page
Wait - Wait for a specific amount of time
- (int) seconds to wait
Explicit Action Types
Click - Click on an element in the page
- (str) component to click on
Input Text - Input text to a text field in the page surrounded by curly braces. An example would be Input {{test@gmail.com}} into the email field
- (str) text to input
Scroll Down - Scroll down on the page
- (str) component to scroll on
Scroll Up - Scroll up on the page
- Optional (str) what component to scroll up on
Scrape - Scrape specific json data from the state
- Pydantic model type that you would like
Swipe - Horizontal swiping
- Optional (str) Component to swipe on
Select - Choose a selector from the dropdown
- (str) Choose a selector to choose from
Hover - Hover over a component
- (str) Component to hover over
File Upload - Upload a file to the page
- (file) File to upload
Step Settings
Clicking on the 3 dots on a step will expand the step to show the settings for the step.
Vision - Use a screenshot while running the step. Useful for cases where the DOM is not explicit about the component in interest.
Download - Download a file from the page. The downloaded file will appear in the test report.
Locate - Locate a component on the page. This will highlight the component on the page.
Input Selector - A selector that has been cached for the step. May be an xpath, css selector or a text value. The selector is the first method used to locate the component.
Recording Steps
To record steps, use the “Record” button. This allows you to perform actions on the cloud device, and each action will be automatically converted into a step in your test script. Once finished recording, click the “Stop” button that has replaced the “Record” button.