Feature Friday – Best Test Building Practices With Auto-Suggest
We all have it in one form or another – whether it is on our cell phones, in our emails, or on social media. Auto-suggest as a feature is spread far and wide across the internet and in nearly every aspect of our lives now. Auto-suggest features help users make choices more easily and quickly. On our phones when messaging, we are offered suggestions as to what words we were attempting to type or starting to type. It helps us expedite our messaging. What if the same were possible for testing on Qyrus? Well, today, Brett and Amy are glad to tell you more about our auto-suggest feature and how it can help you expedite your test building process.
Tell us more about auto-suggest offered by Qyrus.
Auto-suggest is a new enhancement that was recently added to the Qyrus platform. There are many ways that we can speed up the test building process on Qyrus, one obvious being our library of different action types that allow users to easily choose what they want to do in a step.
Our use of simple, codeless action types help make test building simpler. However, with the auto-suggest feature enabled, everything becomes a bit quicker. Instead of having to find the specific action type from our list that you would like to use, start typing in the step description field and watch Qyrus work its magic!
Qyrus analyzes what is put into the description field and chooses the action type for you based on what it can infer. For example, if a user wanted to click on a button, they could provide that in the step description and the click action type would be chosen for them. This goes for other action types, as well, like set, verify, and more.
What is the overall impact on the testing process?
Specifically, this targets the test building process. Overall, it really lets users get into a flow and spend less time fiddling with the UI and menus. It is also super intuitive to use.
As simple as it sounds, over time through repeated use, auto-suggest can help save a lot of time and resources. Qyrus has many action types, and although that is a good thing as it helps testers cover a wider range of scenarios, it can also come at a detriment to newer users or those who are seeking to quickly build out tests. Auto-suggest helps combat this.
How might this feature help testers, developers, and business technologists? What value can this feature bring?
From the tester’s perspective, this helps expedite the test building process, as we mentioned before. This can help them cover more test cases and at a faster pace. It also can aid in the learning of the platform and its various action types. One does not necessarily have to know the complete list of action types but can instead describe what they would like to do.
Auto-suggest can also help developers create tests of their own like for unit tests. And from a business technologist’s standpoint, it makes Qyrus even easier for them to jump in and start using and comprehend. They can also quickly create test steps and scripts using auto-suggest.
How do you see this impacting day-to-day operations across organizations?
As we’ve mentioned before, it helps save time and resources – and thus money – in the form of reducing the amount of time that it takes one to build a test script. Instead of having to repeatedly enter in step info and choose action types, it helps testers do it automatically.
What’s more is that this is all an augmentation of our already easy, super simple, and intuitive test building process.
As we can see, there are many benefits that can come from using auto-suggest. The whole point of these tools is to help testers during their day-to-day work and throughout the testing process – from start to finish. At Qyrus, we’re always seeking new ways to further enhance and enable testers for better, more efficient testing. Join us next week to learn more about the platform and all the different features that it encompasses!