Information is the lifeblood of businesses these days; after all, how are you supposed to make smart and informed decisions without the right data? This is especially true in QA when the results of testing can impact development strategy and uncover bugs or the need for new features. Therefore, when choosing a new tool, it’s important to know what kind of data it’ll give you and in what way. A long list of confusing data is sometimes as bad as no data at all if you can’t make sense of it. But we’ll be checking out how Virtuoso presents data in an easy-to-read format to support and streamline your decision-making! 

We have so many dashboards, it can kind of make your head spin, so let’s go through them all! First up is the dashboard that pops us when you look at your goals. This will give you a synopsis of the tests in that goal, and then once you click a goal, you can see the pass/fail overview of each journey. 

When you click on a journey, you get this great breakdown of statistics (see above). Not only do you see how many steps there are in the journey (top right), but you also get the details on network requests, browser logs, and performance metrics (to get these, you need to run your journey with an advanced execution with snapshots toggled on). The performance metrics include the time to the first byte, the first input delay (how long it takes from the first interaction like clicking a link to the response from the browser, the largest contentful paint (similar to the first input delay, and measured in seconds), and the first contentful paint (the time from when the page starts loading to the content being rendered). Finally, you even get a nice line graph of execution health trend and activity duration on dates run.

‍

After you’ve run a journey and get taken to the run page, you get another look at how many tests have run and the pass/fail ratio on the right hand of the screen (pictured above). You also get information on who ran the test, what environment, what browser, and what screen size the test was run on. 

On the left, you see the journey steps and everything that happened to each step (pictured below). The little horizontal dashes mean that it made either a network request or generated a console log. The band-aid represents a step that self-healed (each step with this symbol is a place where you’ve been saved a bunch of debugging and work!). Finally, the pyramids indicate that the step has side effects, for example, an API call. 

Maybe for some reason, you don’t like a step that self-healed? Well, by clicking on the self-healing tab, you can either accept or reject the changes made with the cross or tick. 

Then in the next tab over, you can check on all the side effects that the journey produced, like API calls, pop ups, or downloaded files. 

On the flip side, here’s what a dashboard of a failed journey will look like. It will list which checkpoint and step contained the bug along with the reason, so you know exactly what’s going on when a test fails.

So, do you think those are enough dashboards to give you all the information you need? If you think you do need more, be sure to let us know! We have a whole channel dedicated to feature requests in our Discord server, so you can drop us a message there if there’s something else you want to keep track of. You can see all these stats for yourself by authoring your own tests in under 15 minutes! Give our 14-day, no-strings-attached free trial a shot to see how fast your pages are responding to your user input.