{"id":1841,"date":"2014-10-30T01:04:48","date_gmt":"2014-10-30T05:04:48","guid":{"rendered":"http:\/\/qxf2.com\/blog\/?p=1841"},"modified":"2017-07-06T14:52:10","modified_gmt":"2017-07-06T18:52:10","slug":"naf-issue-mobile-testing","status":"publish","type":"post","link":"https:\/\/qxf2.com\/blog\/naf-issue-mobile-testing\/","title":{"rendered":"What is NAF ?"},"content":{"rendered":"

UIAutomatorViewer is a tool to inspect and identify UI elements in Android apps<\/a>. However not every UI element you see is accessible to UIAutomatorViewer. Sigh. I know. That sucks. But at the very least, UIAutomatorViewer lets you know which of these elements are not accessible. <\/p>\n

I was messing around with Appium<\/a> and DroidFish<\/a> secretly hoping to write an automated test that would play out a famous chess game. I noticed that I was able to identify the chessboard but not the individual squares. Most parts of the app were identifiable using UIAutomatorViewer. For example, the buttons are easily identifiable in the UIAutomatorViewer as shown in the image below:
\n\"notNAF\"<\/a>
\nThe chess board however is slightly different. In the UIAutomatorViewer you can see that NAF is set to true in the Node Details.<\/p>\n

\"chessboard_NAF\"<\/a><\/p>\n

What is NAF ?<\/h3>\n

NAF means Not Accessible to Framework and only limited information may be available for these components. So if you want to automate a workflow involving a NAF element – well, good luck! I hope you have good relations with the developer and can request them to make a change to the application. <\/p>\n

As a workaround, I decided to move the chess pieces by using the co-ordinates. This is not recommended<\/b><\/u>. The co-ordinates will change for each device you test on. Do not use this approach unless you have no other option. <\/p>\n

\"f7\"<\/a><\/p>\n

\"f5\"<\/a><\/p>\n

To assert that the correct move is played, I used the moveList – which thankfully is not NAF.
\n\"moveList_assert\"<\/a><\/p>\n

NOTE:<\/strong> I have reported the same on appium-discuss<\/a> with the hopes that there is a better solution.<\/p>\n

\n","protected":false},"excerpt":{"rendered":"

UIAutomatorViewer is a tool to inspect and identify UI elements in Android apps. However not every UI element you see is accessible to UIAutomatorViewer. Sigh. I know. That sucks. But at the very least, UIAutomatorViewer lets you know which of these elements are not accessible. I was messing around with Appium and DroidFish secretly hoping to write an automated test […]<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[50,15],"tags":[],"class_list":["post-1841","post","type-post","status-publish","format-standard","hentry","category-appium","category-how-to"],"_links":{"self":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts\/1841","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/comments?post=1841"}],"version-history":[{"count":12,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts\/1841\/revisions"}],"predecessor-version":[{"id":6389,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts\/1841\/revisions\/6389"}],"wp:attachment":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/media?parent=1841"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/categories?post=1841"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/tags?post=1841"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}