How to scroll to element in XCUITest

When it comes to mobile test mechanisation, prefer the correct framework is crucial for fastness, reliability, and cross-platform coverage. Two widely use frameworks areEspresso and Appium. While both are powerful, they serve different testing needs, making it crucial for QA teams to realize their forcefulness, limitations, and differences.

This clause excuse in particular the differences betweenEspresso and Appium, covering their features, vantage, limitations, and a direct comparability to help team choose the rightfield mobile automation framework.

What does scroll to an element mean?

Mobile user, ofttimes noticehook downwith their fingerbreadth to read/access the sections that are not seeable in the current displayed area of the blind. The swiping gesture to hit an element across the length of the page as seen below is ring Scrolling to an constituent.

Scroll down in App Store

Pro tip: Tools like SUSA can handle this autonomously — upload your app and get results without writing a single test script.

Scrolling down employ XCUITest

You can scroll or swipe down in an app without any constraints as well as conditions. It can be a generic scroll/swipe as good as a scroll with a condition.

Let us go through an model where we just scroll down generally in an app:

Code to Scroll down Once using XCUITest

functest_ScrollDownInApp () {appStore.swipeUp ()}

Running XCUITest Test on Real iOS Device

Here ’ s how running an XCUITest on a Existent iOS twist would seem like.

Scroll Down Once

Locate Elements using BrowserStack App Live – Inspect Beta

Before scrolling or swiping down an app, it is a good practice to locate elements in the app and pinpoint the destination of the scroll.

Debugging apps for locating elements before scrolling is crucial. One easiest way to inspect iOS app elements easily is to place element using – Inspect Beta. BrowserStack App Live is a real device cloud where you can access various Android and iOS devices and run tests on them.

How to Scroll down to Element using XCUITest

In the below piece of codification, we would discover that we are scrolling till an element is launch without any set bound with any sure number of scrolls.

Approach 1 & # 8211; Generic Scroll/Swipe down

functest_FootBall_AppTap_In_AppStore () {appStore.launch ()letgameRequired = `` eFootball™ 2022, Authentic football game! ''letfootballLabel = appStore.buttons [gameRequired]while! (footballLabel.exists) {appStore.swipeUp ()} XCTAssertTrue (footballLabel.isHittable)}

Running XCUITest with Generic Scroll on Real iOS Device

Scroll Down till Element is found

Drawback of Generic Scroll

If the element is not found, there is a possibility of the swipe to enter a loop until the exam fails, leading to unwanted wastage of time and execution. Hence, we need a better approach, where the number of scrolls needs to be defined to handle such unforeseen situations.

Approach 2 & # 8211; Pre-defined Scroll/Swipe down

Here, the routine of ringlet is between 0 & amp; 10 depending upon where it finds the element sooner. So if the element is found in the 5th coil, it will scroll only 5 times. If an ingredient is not found within 10 scrolls, then the test fails.

 functestScrollMaxTime () {letgameRequired = `` WWE Mayhem, No1. WWE Arcade Action Game '' appStore.launch () appStore.tabBars.buttons [`` Games ''] .tap ()letlastCell = appStore .scrollViews .cells [gameRequired] .firstMatchletmaxScrolls = 10var count = 0



        whilelastCell.isHittable ==false& amp; & amp; count & lt; maxScrolls {appStore.swipeUp () count += 1}letbuttonLabel = appStore .buttons [gameRequired] .firstMatch .label XCTAssertEqual (gameRequired, buttonLabel)}

Running XCUITest with Approach 2 on Existent iOS Device

Scroll Down with Defined Condition

It is always commend to write test scripts with handled scenarios for error and exceptions. Bear in mind to compose trial that not merely passing but also fail efficaciously, in case of an error/issue.

Conclusion

For exact test results, it is always recommended to run trial on, so that the can be taken into account. Moreover, since different device have different screen sizing, hence in the case of pre-defined scroll the number of curlicue might be altered establish on the device mode. Hence, try testing on real devices to get accurate results and deliver a consistent user experience.

, allows QAs to test their mobile apps on existent devices instead of emulators or simulators under real-world scenario. While, allows QAs to run Automated tests on XCUITests for better execution. Test results can be viewed on App Automate Dashboard once the trial executing is completed. By snap on individual tests will give you a detailed report for each test include steps,, Appium lumber, execution video log, and other details for best debugging of failed examination.

Related Guides