Added Android device commands#518
Added Android device commands#518TikhomirovSergey merged 26 commits intoappium:masterappium/java-client:masterfrom SrinivasanTarget:AndroidDeviceCommandsCopy head branch name to clipboard
Conversation
…ouchActionSplitting
…arget/java-client into SrinivasanTarget-TouchActionSplitting
- new interfaces were added - deprecated API
- new methods were added to MultiTouchAction - AppiumDriver methods which perform multiple touch actions were marked as Deprecated - Constructors of TouchAction and MultiTouchAction were changed. Now it accepts any instance that can perform touch action and multiple touch actions.
- the new interface CreatesSwipeAction was added. - the reversion of last changes of TouchableElement. - the `swipe` is deprecated method.
- CreatesSwipeAction API was implemented - SwipeElementDirection was redesigned - constructors of TouchAction and MultiTouchAction were improved.
- also code issues were got fixed
- IOSSwipeGestureTest was added
- the swiping combined with the tapping.
…b.com/TikhomirovSergey/java-client into TikhomirovSergey-SrinivasanTarget-TouchActionSplitting
Fixed Codacy errors Fixed Codacy errors
…ikhomirovSergey-SrinivasanTarget-TouchActionSplitting
… of https://github.com/SrinivasanTarget/java-client into AndroidDeviceCommands
|
@imurchie Can you please check this? https://gist.github.com/SrinivasanTarget/d564095d2009779bed69a2d6ef8f0b8e. I'm running from source with latest android driver and base driver. |
|
@SrinivasanTarget This should be a |
|
@TikhomirovSergey Have fixed this PR. Tested this on Android 6.0 and it works as expected. |
Refractoring
|
This PR is in the conflicted state |
|
Yup @TikhomirovSergey Will close this and raise a new one probably in sometime. |
…ndroidDeviceCommands
|
@TikhomirovSergey I have rebased this to master and fixed the conflicts now. |
|
|
||
| import java.util.Map; | ||
|
|
||
| public interface HasDeviceDetails extends ExecutesMethod { |
There was a problem hiding this comment.
It seems that methods that declared by this interface are Android-specific. Please take a look at
https://github.com/search?q=org%3Aappium+DISPLAY+DENSITY&type=Code
https://github.com/search?q=org%3Aappium+GET+SYSTEM+BARS&type=Code
I think it has more sense to move this interface to the io.appium.java_client.android
| import io.appium.java_client.CommandExecutionHelper; | ||
| import io.appium.java_client.ExecutesMethod; | ||
|
|
||
| public interface IsKeyboardShown extends ExecutesMethod { |
There was a problem hiding this comment.
I think it has more sense to unite this interface with HasDeviceDetails
| assertNotNull(radioGroup.getLocation()); | ||
| } | ||
|
|
||
| @Test public void deviceDetailsAndKeyboardTest() { |
There was a problem hiding this comment.
Why this method is here? Maybe it has more sense to move it to AndroidDriverTest
|
@TikhomirovSergey Fixed review comments now |
|
@TikhomirovSergey Ping |
Change list
Added Android device commands
Types of changes
What types of changes are you proposing/introducing to Java client?
Put an
xin the boxes that applyDetails
Added Android device commands
Added,
io.appium.java_client.android.IsKeyboardShownAPI andio.appium.java_client.HasDeviceDetailsAPI.@TikhomirovSergey Please review