I’m about as far from a tech person as there is. My interests lie in dead languages, historical events that happened strictly in BC, and writing Dungeons and Dragons campaigns by hand (set in Ancient Italy and Greece, naturally). I even got a hoity-toity (and now rather un-used) Master’s degree in Classics - the only computers involved there were to read articles written in the early 20th century! So, when I tried out Virtuoso for the first time, admittedly I was a little skeptical about how codeless it really was. Even though coding is similar to learning languages, it’s always looked like math to me; and I hate math. I definitely thought Virtuoso was going to be more complicated than it looked. Besides, I hadn’t even considered that there would need to be teams of people to test websites to make sure nothing broke.
It was fairly easy to navigate through creating a goal and then a journey, so I was able to quickly get started in writing my test. I wanted to start with something easy and something that I was familiar with, so I decided to test logging into Etsy (I buy way too many sets of artisan dice). I was surprised at how intuitive the Natural Language Programming was! Virtuoso understood when I gave it the command “type” instead of “write”, and I didn’t have to specify that “email address” was a field; it filled that in on its own. I just told Virtuoso to fill in my email and my (now changed) password then clicked the execute button!
If you watched my incredibly professional video above, you’ll notice that I did have a technical glitch. The first time I ran the test, it failed because there was a popup about accepting cookies that I hadn’t realized was there. Luckily, with Virtuoso’s snapshot feature, it was easy to click on the step that had failed to see a screenshot of exactly what had happened. Then I was able to adjust and easily add in another step to account for that popup.
One of the things I really liked was the dashboard for each goal. It was organized well and simple enough that I could understand the data it was showing me. But, there were also tabs with more advanced options, so if I even knew the bare minimum about testing, the data there could be really helpful. But because everything is organized in tabs, I don’t have to see data that I don’t understand.
Overall, this was a very simple test that I ran. Next, I’m going to author a more complicated test that is about buying an item and inputting a lot more information like (fake) credit card info and addresses. Stay tuned!
How to shift your testing left and build web automation that keeps up with your development.Download eBook