We're super excited to share the latest 2 Steps New Features demo with you.
2 Steps v6 is designed to increase observability by making automated user transactions even more robust and flexible.
In this demo webinar, you'll learn what new features we have added to enhance synthetic monitoring across your platforms
Fill out the form below to watch our demo and learn more about 2 Steps Synthetic Monitoring, natively designed for Splunk.
2 Steps v6 Overview
2 Steps now supports “element matching” as an alternative to image matching in Chrome tests. This major new functionality allows 2 Steps to handle many previously difficult scenarios, for example when the target of a command is pushed off the bottom of the screen or hidden by a popup, or when a style update changes the appearance of a button.
When building and running tests in interactive mode, the image matched at each step is highlighted and the position of the mouse at each click is displayed, making tests easier to follow and debug.
Three new commands have been introduced:
An “Else” command has been added to complement the “If Image is Visible” and “If Text is Found” commands, allowing for an alternative execution flow if the “if” condition is not met.
“Extract Text with OCR” allows text to be read from part of the screen into a test variable.
A test can now be embedded inside another test as a set-up step. This makes it possible, for example, to record a login procedure and then embed it into multiple tests, avoiding the need to re-record the login process each time, and making test maintenance easier.
The schedule app has been improved:
As schedules are added and altered, live feedback is provided on how many test runs will be required over the license period, making it much easier for customers to optimise scheduling for their license.
More filtering options are provided and tests may be deleted from the schedule app, making test maintenance easier.
Variables can now be emitted to the test results which are sent to Splunk, allowing for custom metrics based on variable values set during test execution.
Test timing thresholds have been simplified by removing test-level thresholds altogether and deriving them instead from the individual checkpoint timing values. This eliminates the possibility of the common mistake of failing to update test timings when checkpoints are added or changed.