We should avoid hard coding of paths in tests as this adds to portability of test from one machine other.
Next appium and Android mobile app automation video tutoria l is live. If you are new to appium then please check - appium-tutorial This video tutorial covers - Start vysor (Just for this session and not mobile automation :)) Start appium and start appium inspector Desired Capabilities platformName - Android deviceName - L2N0219828001013 (as seen on "adb devices") Saved Capability Sets Start Session Scan app elements using appium inspector Get appPackage and appActivity using "APK info" app Install "APK info" app and open app whose appPackage and appActivity are required i.e. calculator Check top section of app icon com.android.calculator2 is app package com.android.calculator2.Calculator is app activity testng.xml file settings for running Android app tests Test details com.seleniumtests.tests.mobile.AndroidAppTest and CalculatorScreen class View beautiful STF test report
FYI: You can use Environment("varname"), you don't need the ".Value".
ReplyDeleteGood work otherwise!
How can we follow same practice in Selenium Automation Project?
ReplyDeleteExample: System.setProperty("webdriver.chrome.driver",
"D:/automation/myproject/src/chromedrivers/win7/chromedriver_2.exe"); or in pom.xml
C:/Users/OfficePC21/workspace/deletexslt/testxslt/testng.xml