The holiday rush is officially over! With this holiday season now in the rearview mirror, it\u2019s time to look forward to the road ahead and get prepared for an undoubtedly busy 2023. But don\u2019t worry, Qyrus isn\u2019t throwing on the breaks anytime soon when it comes to features! This week, we are joined by Daniel and Joyal from our Chicago Qyrus team to learn more about some new mobile native locator strategies that have been introduced to the Qyrus platform. Without further delay, let\u2019s race into this topic!<\/p>\n
Daniel:<\/strong> Joyal:<\/strong> Daniel:<\/strong> \u200d<\/p>\n For the reader\u2019s benefit, we have provided an example below:<\/p>\n Example of XPath on iOS: As a class chain, this XPath can look like this: But using a predicate string, it could look like this: Daniel:<\/strong> Joyal:<\/strong> \u200d<\/p>\n Qyrus is always looking to push the limit when it comes to developing new tools and strategies to help enable better testing across the board for everyone involved. This is not limited to different levels or types of testers, but also to less technical personnel.<\/p>\n Joyal:<\/strong> Daniel:<\/strong> Joyal:<\/strong>
\nQyrus mobile testing now has support for 3 native locator strategies when users are building out their test scripts. There are two that are supported for iOS\u2014class chain and predicate string\u2014and one for Android: UIAutomator.<\/p>\n
\nThis is helpful for those mobile testers who are more experienced. Native locators can speed up test executions by improving the performance of locating the element. There are elements out there that cannot be found by using ID, name, accessibility ID, or XPath locator types.<\/p>\n
\nEven though this strategy is the most common out there and platform-agnostic\u2014that is to say, it works for both iOS and Android devices\u2014it can be the most time-intensive choice. By choosing a native locator strategy, a tester can leverage the flexibility that an XPath can provide without incurring a performance penalty.<\/p>\n
\n\/\/XCUIElementTypeOther[@label=’login’)]<\/strong><\/p>\n
\n**\/XCUIElementTypeOther[label matches “login”]<\/strong><\/p>\n
\nlabel matches “login”<\/strong><\/p>\nWhat is the overall impact this might have on the testing process? <\/em><\/h5>\n
\nWe can see this having an impact during the test-building phase when users are creating and building up their catalog or suite of test scripts for execution. This can help expedite the test-building process since, to an experienced mobile tester, using something like a predicate string is much quicker than having to get an XPath for every element.<\/p>\n
\nNot only that, but since we see faster run times, we can say there\u2019s a definite impact on test executions. The new native locator strategies provide an overall speed boost to the testing process as a whole.<\/p>\nHow might these new native locator strategies help testers, developers, and business technologists? What value can this feature\u202fbring?\u202f <\/em><\/h5>\n
\nWell, as we mentioned before, an advanced tester might find the most use out of this feature. In general, it makes their testing experience easier. But besides that, using a predicate string also makes it easier for less technical users of Qyrus to understand what is being searched for. Seeing \u201clabel matches \u2018login\u2019\u201d makes it much easier to understand what the test is looking for than a long, exhaustive XPath.<\/p>\n
\nAnd for developers, they\u2019d find use in this, much similar to a tester. It would make their unit testing and quick tests much easier to create, run, and maintain in the long run.<\/p>\nDoes the same or similar functionality exist without Qyrus, and how do competitors address similar problems?\u202f <\/em><\/h5>\n
\nThere are a few competitors out there that do offer all these strategies already, but on Qyrus we are striving to make these strategies more usable for both experienced and newer testers.<\/p>\n