Change log:

• AppiumDriver has become abstract. @Jonahss I got your point.
• AndroidKeyCode has been moved to "android" pakcage
• AndroidDriver implements FindsByAndroidUIAutomator. IOSDriver implements FindsByIosUIAutomation. AppiumDriver still implements FindsByAccessibilityId.
• SELENDROID_PORT has been added to MobileCapabilityType
• update to Selenium 2.43.1
• Tests have been moved, so it is convenient to run tests for each platform

• Test coverage is increased. I have add AndroidAccessibilityTest and AndroidContextTest.

Note!!! AndroidContextTest. There are

//TODO 

comments.
I think there is a bug. AndroidDriver can't be run with Selendroid and activity defined in capabilities.

Awesome work!
Aha, android activity capability and selendroid don't work? Can you create a github issue on the main Appium project?

Yeah! It doesn't work. An issue is coming soon.

appium/appium#3698

Let AndroidContextTest stay as it is until issue is resolved.

Oops, just found I never added my AppiumDriverTest to the repo... >.<

So, the tests for java-client can be very lite. We don't really need to test appium functionality, just that the client sends the right requests, and is able to parse responses. So things like Context, only need to be tested once for AppiumDriver, rather than separately for ios and Android. I'll show you what I plan in a pull request tomorrow, for now, don't worry about it ^.^

Thanks, @Jonahss! I am looking forward to seeing something interesting.

If you can please put your new commits by 14:00 (2 PM) (US, California). I can do something till
1:00 (1 AM) (Russia, St. Petersburg).