The green shoots of Spring are upon us and it’s time to get an update on what has been going on with our continuous release strategy.
The green shoots of Spring are upon us, many of us are surrounded by daffodils, and it’s time to get an update on what has been going on with our continuous release strategy. Our most recent incarnations let you work more intuitively, do more with less clicks, and easily get to the very route of testing challenges. Let’s take a look
Understand every project’s journey at a glance and see the very latest modification and execution status. Get organised with the ability to filter and sort your journeys. Then save time and effort by re-executing journeys individually or in bulk.
Save time and get control over your test maintenance at your fingertips. When a test has failed you can fix an element by interacting with a screenshot. Simply hover over any element, receive the information you need, and click fix. Then re-execute your journey to smash your maintenance overhead out of the park.
Can your application only be accessed through a http proxy or requires that all traffic targeting the application is directed through a http proxy? Not a problem, you can now use Virtuoso’s bridge proxy support to run tests redirect traffic targeting your application through a proxy server. Take it further and run third party apps such as Owas Zap to get even more application analysis.
Get absolute reusability across all your tests and accelerate your test authoring. Write and extend similar journeys by using the same checkpoint multiple times. Should any test fail, simply fix the checkpoint once and repair all journey’s using that checkpoint.
Receive instant feedback on how your journeys are performing. Understand if checkpoints are passing or failing in real time. Get detailed screenshots and information on step execution progress to make complicated and robust tests faster.
.jpeg)
Knowing that a test step has failed can be an indication of a bug or regression but may also be a number of other things (e.g., test needs maintaining). Establishing what caused the test to fail is vital to both validate that the application under test is working as expected and, if not, how to fix it.
Virtuoso's root cause analysis helps you do just that. At a glance, get execution and change history, visual comparisons, and much more, to understand the underlying reason for failures.
Ensure your entire team knows both what you are doing and why. Leave comments as steps anywhere in a journey to clearly raise action points such as TODO or FIXME.
You can get detailed information on all the new Virtuoso features by visiting our changelog. If you want to get first hand experience of Virtuoso then why not book a demo?
