{"id":2623,"date":"2015-03-24T12:30:41","date_gmt":"2015-03-24T16:30:41","guid":{"rendered":"http:\/\/qxf2.com\/blog\/?p=2623"},"modified":"2018-03-15T10:38:09","modified_gmt":"2018-03-15T14:38:09","slug":"python-appium-scroll-through-search-result-table","status":"publish","type":"post","link":"https:\/\/qxf2.com\/blog\/python-appium-scroll-through-search-result-table\/","title":{"rendered":"Python and Appium: Scroll through search result table"},"content":{"rendered":"

In this post we show you how to scroll through a table and identify elements. We also tackle the case where the table spans multiple pages. This is a natural and common workflow on most mobile devices. A typical use case involves the user performing a search within a mobile application. The app returns a table of results. The user then scrolls through the results and clicks on the result she likes. <\/p>\n

\n

Why this post?<\/h3>\n

Qxf2\u2019s top goal<\/a> is to help testers. We identified mobile automation as one area where we could help testers. Over the past few months, we have written several basic tutorials that help testers with mobile automation. We feel like the next stage is to address some common intermediate level problems you may face as you implement mobile automation at your workplace. This post outlines a technical challenge testers are likely to face and our approach to solve it.<\/p>\n

\n

New to mobile automation?<\/h3>\n

If you are new to mobile automation, we suggest the following posts to get started:
\na) Run Appium on an emulator<\/a>
\nb) Run Appium on mobile devices<\/a>
\nc) Identify UI elements on mobile platforms<\/a>
\nd) Execute different mobile gestures<\/a><\/p>\n

\n

Overview<\/h3>\n

We are going to be using BigBasket<\/a> as the example mobile application. We will login, search for a product, scroll through all the search results and print out the products we encounter in the search results. In previous posts, we have shown you how to login to BigBasket<\/a> and perform a search<\/a>. Here is a short video (with no audio) showing you what actions our automated script intends to perform. We used the excellent Recordable<\/a> app to create this video.
\n

\nhttps:\/\/qxf2.com\/blog\/wp-content\/uploads\/2015\/03\/10-03-2015-12-071.mp4<\/a><\/video><\/div><\/p>\n

We are searching for ‘Real juice<\/em>‘ using the BigBasket application. Once we click on the search icon we note that 20 items out of the total 24 items are displayed on page 1. We need a way to iterate through these first 20 search results, print out each one of them and then click on the ‘Next’ button to view the remaining 4 items. We are choosing to print out the title of every product we notice while scrolling. This is to show you how to pick a specific element\/column from a table!<\/p>\n

\n

Algorithm for scrolling through tables<\/h3>\n

The logic for collecting each search result deserves some explanation. Search results are usually multi-page, which means it is not enough to just collect the results on the first page. We need to be able to paginate intelligently too. Further, given that the scroll size is arbitrary, we have to ensure we collect each search result exactly once and miss no search result. If your table does not paginate, simply skip the pagination portion of the logic.<\/p>\n

\"Flowchart<\/a>
Flowchart for how to scroll through tables using Appium<\/figcaption><\/figure>\n
\n

Code to implement scrolling through tables<\/h3>\n

Here is the code snippet for implementing the flow chart above. We use a counter to keep track of the number of elements traversed. The counter is helpful while debugging. <\/p>\n

\r\ndef get_search_result(self,results_count=0):\r\n        \"Get and scroll through the search results of the query\"\r\n        elm = self.get_element(self.first_element_tablerow)\r\n        elm_prod_desc = elm.find_element_by_id(self.search_result_text)\r\n        new_prod_desc = self.get_dom_text(elm_prod_desc)\r\n        #Case when we cant scroll further,we get all elements present on the screen\r\n        if (new_prod_desc == self.current_prod_desc):\r\n            results = self.get_elements(self.search_result_text)\r\n            for result in results:\r\n                search_result = self.get_dom_text(result)\r\n                #To avoid counting the top element twice\r\n                if (search_result != new_prod_desc):\r\n                    results_count = results_count + 1\r\n                    self.write(\"Item number %d is %s\"%(results_count,search_result))\r\n            #Click 'Next' button if present\r\n            if (self.check_element_present(self.search_next_button)):\r\n                self.click_element(self.search_next_button)\r\n                self.wait(3)\r\n                self.get_search_result(results_count)\r\n                self.wait(3)\r\n            else:\r\n                self.write (\"Reached end of search results\")\r\n        else:            \r\n            self.current_prod_desc = new_prod_desc\r\n\r\n            #######################\r\n            #TO BE FILLED IN THE SWIPE, MOVE_TO SECTIONS OF THIS TUTORIAL\r\n            #option 1 : swipe, option 2:move_to\r\n            #######################\r\n\r\n            results_count = results_count + 1\r\n            self.write(\"Item number %d is %s\"%(results_count,self.current_prod_desc))\r\n            self.get_search_result(results_count)\r\n<\/pre>\n
\n
Approaches<\/h3>\n
While all this seems handy and neat, a big problem happens to be how much to scroll. If you scroll too much, you run the risk of missing some search results because they were never displayed. If you scroll too little, this GUI test could take forever! So we experimented with two approaches:
\n1. Swipe
\n2. move_to
\nIt turned out that we have more control with move_to. Use our previous tutorial<\/a> to move out the amount you want move_to to move into a configuration file. For the completeness of this post, we will show you both methods.<\/p>\n
1.Using swipe:<\/strong>
\nInitially we went ahead implementing the scroll functionality using the swipe method (bottom-up), but we realized the results were not consistent and few elements were getting missed while iterating over the search results.<\/p>\n
\r\n#swipe from the bottom of the screen to the top of the screen\r\nself.driver.swipe(470, 800, 470, 50, 400) \r\n#swipe the top element \r\nself.driver.swipe(470, 420, 470,180, 400) \r\n#swipe the last element swipe  \r\nself.driver.swipe(470, 800, 470, 600, 400) \r\n# swipe from middle of top element to the top of screen\r\nself.driver.swipe(470, 280, 470, 80, 400) \r\n<\/pre>\n
While our first instinct was to use swipe, Appium can only ‘see’ elements visible on the screen. So if you swipe hard, you run the risk of overshooting and having some elements not display at all.<\/p>\n
2.Using move_to:<\/strong>
\nNext we tried the move_to method where we identify the element using the tablerow xpath and move it to the top of the screen so that the next item is the first item on the screen. We called it recursively till all the elements are traversed successfully. This approach gave us accurate results.<\/p>\n
\r\nfrom appium.webdriver.common.touch_action import TouchAction\r\n\r\naction = TouchAction(self.driver) \r\naction.press(elm).perform()\r\naction.move_to(x=0, y=50).perform() #We highly recommend moving the '50' into a conf file\r\nself.wait(2)            \r\n<\/pre>\n
Here is the final test script for test run<\/p>\n
\r\n\"\"\"\r\nQxf2 test case to Search for a item in BigBasket app. This class imports BigBasket_Base_appium \r\n\"\"\"\r\n\r\nfrom BigBasket_Base_Appium import BigBasket_Base_Appium\r\nfrom optparse import OptionParser\r\nfrom ConfigParser import SafeConfigParser\r\n\r\ndef run_search_test(config_file,test_run):\r\n    \" Perform search for the value supplied and list the search results\"\r\n    #Create a test obj with parameters\r\n    test_obj = BigBasket_Base_Appium(config_file=config_file,test_run=test_run)\r\n    test_obj.wait(10)\r\n    test_obj.click_search_home()\r\n    test_obj.perform_search(\"real juice\")\r\n    test_obj.get_search_result()\r\n    test_obj.wait(5)\r\n    \r\n    \" TearDown Test\"\r\n    test_obj.tearDown()\r\n    \r\n     \r\n#---START OF SCRIPT\r\nif __name__=='__main__':\r\n    #Accept command line options from the user\r\n    #Python module optparse \r\n    usage = \"usage: %prog -c  -t  \\nE.g.1: %prog -c D:\\\\Git_Qxf2\\\\qxf2\\\\samples\\\\clients\\\\BigBasket\\\\configuration.ini -t \\\"Android_4.2\\\"\\n---\"\r\n    parser = OptionParser(usage=usage)\r\n    parser.add_option(\"-c\",\"--config\",dest=\"config_file\",help=\"The full path of the configuration file\")\r\n    parser.add_option(\"-t\",\"--test_run\",dest=\"test_run\",help=\"The name of the test run\")\r\n    (options,args) = parser.parse_args()\r\n\r\n    run_search_test(config_file=options.config_file, test_run=options.test_run)\r\n<\/pre>\n
Now you can run the test with the command line parameters mentioned here<\/a>. <\/p>\n
\"run<\/a><\/p>\n
And finally, here is a recording of the entire automated test.
\n
https:\/\/qxf2.com\/blog\/wp-content\/uploads\/2015\/03\/10-03-2015-11-561.mp4<\/a><\/video><\/div><\/p>\n
\n
Phew! We needed video, diagrams, code snippets and a whole lot of text to write up this tutorial. We also had to leave out a lot of code and share only the snippets. We plan on sharing our code on GitHub sometime this year. Until then, if you need help with some of the missing code, feel free to ask us below. <\/p>\n
Note: <\/strong>We think you would be interested in our open-sourced Appium + Python test automation framework<\/a> based on the page object pattern.<\/p>\n
P.S.: Yes. We are taking baby steps to publishing these tutorials on Youtube.<\/p>\n
\n