I came from the RoR web development and – as we all know – Rails community loves tests. Personally, I am a fan of acceptance testing and using mostly capybara for it. So, when I shifted to the iOS development, it was essential for me to find some decent acceptance testing tools like Apple’s UI Automation, Calabash and Appium. The last one appeared to be a test automation framework of iOS, Android and hybrid apps that supports Ruby among other languages. I’ve chosen it to be the first one to explore and started writing tests for my current real project. Let’s see now whether Appium stack is a good choice for the our purposes.<\/p>\n\n\n\n
To start with, we need 3 things to run integration tests with Appium:<\/p>\n\n\n\n
There are two ways to install Appium: download packaged app or install it via npm. I tried to install it via npm, but it didn’t work, so I opted for a bundled app and successfully ran couple examples. Then, however, I decided to fix my Appium npm install and managed to run it from console by completely reinstalling node and manually cleaning \/usr\/local\/share\/npm<\/i>.<\/p>\n\n\n\n Below is a simple script to create a build and place it inside the desired folder to easily access it from test whenever required.<\/p>\n\n\n\n Don’t forget to make scheme Project shared, otherwise you might get the following error:<\/p>\n\n\n\n Here is the template, so we now need to fill in the flows.<\/p>\n\n\n\n Selenium operates with views similar to HTML DOM elements’ and it looks like this:<\/p>\n\n\n\n Guess how to find tableCells? Right:<\/p>\n\n\n\n To get all elements use<\/p>\n\n\n\n In the end, you will need only visible buttons<\/p>\n\n\n\n Looks good so far.<\/p>\n\n\n\n To click on a button named “Done”, you can use:<\/p>\n\n\n\n In the real world, however, there are too many buttons with custom images; so, in this case we have to use accessibilityIdentifier<\/i>. More docs:<\/p>\n\n\n\n$: sudo npm install -g appium\n$: appium\n<\/pre>\n\n\n\n
Make app build<\/h2>\n\n\n\n
xcodebuild -sdk iphonesimulator6.0 \\\n -workspace \/Users\/mishyn\/workspace\/rw\/project-ios\/Project.xcworkspace \\\n -scheme Project \\\n ONLY_ACTIVE_ARCH=NO \\\n TARGETED_DEVICE_FAMILY=1 \\\n DEPLOYMENT_LOCATION=YES \\\n DSTROOT=`pwd`\/app\n<\/pre>\n\n\n\n
ld: library not found for -lPods\nclang: error: linker command failed with exit pre 1 (use -v to see invocation)\n<\/pre>\n\n\n\n
Write spec<\/h2>\n\n\n\n
def absolute_app_path\n file = File.join(File.dirname(__FILE__), 'app\/Applications\/Project.app')\n raise \"App doesn't exist #{file}\" unless File.exist? file\n file\nend\n\ncapabilities = {\n 'browserName' => 'iOS',\n 'platform' => 'Mac',\n 'version' => '6.0',\n 'app' => absolute_app_path\n}\n\nserver_url = \"http:\/\/127.0.0.1:4723\/wd\/hub\"\n\ndescribe \"Computation\" do\n before :all do\n @driver = Selenium::WebDriver.for(:remote, :desired_capabilities => capabilities, :url => server_url)\n end\n\n after :all do\n @driver.quit\n end\n\n it \"should open search\" do\n @driver.find_elements(:tag_name, '*')\n end\nend\n<\/pre>\n\n\n\nFinding elements<\/h3>\n\n\n\n
@driver.find_elements(:tag_name, 'collectionCell')\n<\/pre>\n\n\n\n
@driver.find_elements(:tag_name, 'tableCell')\n<\/pre>\n\n\n\n
@driver.find_elements(:tag_name, '*').map(&:tag_name)\n# =>\n\n<\/pre>\n\n\n\n
@driver.find_elements(:tag_name, 'button').select(&:displayed?).map(&:text)\n<\/pre>\n\n\n\n
@driver.find_element(:name, 'Done').click\n<\/pre>\n\n\n\n
Set accessibilityIdentifier<\/i> to ‘Done’ in the code, and in the tests use<\/p>\n\n\n\nfind_element(:name, 'Done')<\/pre>\n\n\n\n