Well, if I understand correctly STB tester captures video only through HDMI- is your app and device capable of that ? If yes than you could probably ignore the remote control part of the tester or send dummy commands, then just use the analyzed video results in parallel to appium.

@solTesting, I guess, You are messed up pop-up view and background view in UIAutomator Viewer. If not, Open using Appium inspector. Might you can expect better results !

We used NodeJS to help as out of a similar situation. We designed a mock server on NodeJS and configured REST API to hit Node sever and fetch responses.

Try using appPackage and appActivity in your Desired Capabilities instead of packageName and activityName. DesiredCapabilities caps = new DesiredCapabilities(); caps.setCapability("deviceName", "Android"); caps.setCapability("platformName", "Android"); caps.setCapability("platformVersion", "4.4.2"); capabilities.setCapability("appPackage", "com.example.hybridtestapp"); capabilities.setCapability("appActivity","com.example.hybridtestapp.MainActivity"); driver = new AndroidDriver(new URL("http://127.0.0.1:4723/wd/hub"), caps);

You can get apk using chrome plugin APK Downloader. To install apk use ADB command: adb install path_to_apk_file

There is no programming language called Android. Android is an OS and that as well is developed with Java(I Guess). You can learn and use Selendroid using Java. For Java you will get a lot of help from the countless communities and forums on the internet and is completely open source. Since you are already using Selenium Webdriver with Java, I guess it'll be easier for you to get your hands on Selendroid as well. There are also several other programming languages that you can use, but for you using Java will be more advantageous as you have experience with Java and Selenium! Happy Testing

This question is very broad and is one of those question which is bound to get biased replies based on User's opinions. So when you say, So please suggest which tool should I learn There is no definitive, clear-cut answer, until we understand the projects that are in pipeline are. Nevertheless, on the top of my head, I can name quite a few mobile automation tools here : Appium Calaba.sh Robotium Monkeytalk Ranorex Here is a link of such tools, which I compiled in my blog few months ago : https://qatechnicals.wordpress.com/testing-tools/best-mobile-automation-tools/

Do we have to test on emulators or a real devices for testing mobile applications? Why not both? Some functionality of mobile applications can be well-tested on emulators. Often this mean UI, basic features, etc. Other features may require real devices, particularly if you have device-specific functionality, or functionality that takes advantage of specific hardware features. One approach would be to choose a device and its associated emulator, then test using both. Make note of what could have been tested equally well using just the emulator, and what would require the actual device. Then let that experience be your guide for other devices, and for future versions.

Testing concept will remain same for mobile like UI Testing, functional Testing, Security Testing, Performance Testing and a lot more. But there are lot of things need to check in mobile which is not covered in web testing. This is Good Mobile application testing checklist. Other some example of things, different in mobile testing are : 1 - Testing in different devices. 2 - Testing with different networks like wifi , 4G, 3G, 2G etc. So your Testing cycle will be same just will need different test cases than website.

Have you looked at Appium? I haven't used it but I think it's pretty much selenium for native app testing. http://appium.io/