Provide error if locator is not supported by Selenium Server #1632

Activity

1. sjelin commented on Dec 12, 2014

   

   sjelin

   on Dec 12, 2014

   Contributor

   More actions

   How are you running protractor with selendroid?
2. mitchhentges commented on Dec 13, 2014

   

   mitchhentges

   on Dec 13, 2014

   Author

   More actions

   Oh, that's a fun story, but I'll skip the details :)

   1. Download selendroid and rename it to selendroid.jar for easier typing
   2. Build one of your hybrid apps to make a beautiful little .apk, call it 'app.apk'
   3. Set up your config (see above), where {applicationId} is your application Id (like com.boop.dunks:1234)
   4. Run selendroid. My command-line setup: java -jar selendroid.jar -app app.apk -forceReinstall
      • If you need more verbosity, do: java -jar selendroid.jar -app app.apk -forceReinstall -verbose -logLevel VERBOSE
   5. Run protractor. In my case, node ./node_modules/protractor/bin/protractor config/spec-e2e.js
   6. You remembered to plug in your device, right? ;)

   Two things to keep in mind:

   • Selendroid doesn't like by.model. I fixed this with:

   //Allows by.model with Webdriver
   by.model = function(model) {
       return by.css('[ng-model="' + model + '"]');
   };
   

   • Android opens up the keyboard every time you type. It's like your device wants your tests to fail due to soft keyboards getting in the way. Fortunately:

   //Takes care of the Android keyboard when doing "sendKeys"
   var nativeSendKeys = protractor.WebElement.prototype.sendKeys;
   protractor.WebElement.prototype.sendKeys = function(value) {
       var result = nativeSendKeys.call(this, value);
       browser.actions().sendKeys('\uE100').perform();
       return result;
   };
   

   Don't yell at me for overriding your library functions, I like not having to refactor tests. :)
3. juliemr commented on Dec 13, 2014

   

   juliemr

   on Dec 13, 2014

   Contributor

   More actions

   I'm not sure there's a general way to address this issue. by.model is using the webdriver protocol execute script behind the scenes, which is (I believe) supported to selendroid, it's just something about the implementation is failing?

   We don't test on selendroid at the moment - I think the larger issue here is that Protractor needs to set up some of our test cases with some mobile strategy (figuring out what's at the forefront now - I believe that appium is only using selendroid for older versions (android 2.3-), so I'm not sure if it will feature in our final decision, but this is still pending.
4. juliemr

   added

   status: needs investigation

   on Dec 13, 2014
5. mitchhentges commented on Dec 14, 2014

   

   mitchhentges

   on Dec 14, 2014

   Author

   More actions

   Update:
   by.model works out of the box with Appium.

   If you're considering completely dropping support for Selendroid and focusing on Appium, I would personally recommend against that. In my experience, Selendroid is faster (which is critical on our painfully-slow-running device E2E tests) and Appium has more "hidden" bugs. When testing my app, I've noticed that Appium will fail on clicking certain buttons (the click won't actually go through, but no error is reported) while Selendroid performs the action perfectly.

   I understand that supporting two different frameworks for device testing (Appium due to iOS support, Selendroid due to above - hopefully) is far more difficult, but the benefits are far better for us Protractor end users
6. juliemr commented on Jan 6, 2015

   

   juliemr

   on Jan 6, 2015

   Contributor

   More actions

   I think I'm going to close this issue since the original premise isn't something we need to address. However, deciding on better mobile support is definitely on our todos. We've started to clarify the docs, and better support will be coming soon.
7. juliemr

   closed this as completedon Jan 6, 2015