How to Use the get() Command of AskUI

This tutorial will show you how you can utilize askuis get()-command to write more powerful automation.

Until now askuis-SDK is only allowed to test for the existence of an element with the exists()-command. While that was useful, extracting information about elements such as text was impossible. If you wanted to act based on elements values or assert a state of an element with an assertion library, you could not do that!

With the new get()-command you can extract the information askui inferred. Many more automation possibilities become available 🔥.

We will show you how to assert if a textfield contains a text we tried to insert beforehand. Additionally, we will demonstrate how the get() command works regarding relational selectors as below().

Prerequisites

• You have AskUI installed (Windows, Linux, macOS)
• You can access this practice page

Write to A Textfield

For our test, we first write a mobile telephone number into the textfield Mobile Number on the practice page.

Is There a Textfield Containing our Number?

Let us now see if there is a textfield that contains a text with the mobile number we just entered.

It should print out the following:

Notice that there is no text in there as the mobile number is contained in the textfield as a text element.

Is It the Correct Textfield?

Ok, so there is a textfield containing the correct number. But is it the correct textfield?

Should log this:

With this you can now do assertions with your favorite library or manually:

Additional Considerations for get()

When you use get(), you must pay attention to two details to avoid stumbling upon them.

UI Changes

When the UI changes the detected elements usually change. They may be moved to a new position, disappear entirely, or be populated with new data.

Thus the elements you saved into a variable may get invalid. Be aware of this fact and update your elements when you need an updated version.

Why Is the Sorting All Jumbled up Sometimes?

The get() command returns an ordered list based on the "distance" of the elements. The distance is not entirely based upon physical distance, but also takes into consideration the similarity when you use withText(). It also considers special cases, for example, modal dialogs. Therefore the order can be nonsensical when you look at it from a human perspective!

Let us demonstrate this with an example. With a relational selector, you can do something like this.

Take this example from our practice page:

If you try to get everything above the Submit button, you will get the following elements. The first two elements make sense but the third element seems to be out of order:

If you want to sort it by ymin for example, you have to implement a comparator function and pass it to the sort() function of the array.

For sorting based on the distance of the center of the bounding boxes of each element take a look at this article.

Conclusion

If you pay attention to the pitfalls of get() it is a powerful tool to get more out of your automation efforts.

Get Support

If you have a recurring or persisting issue, don’t hesitate to ask the Discord community for help!

‍