codecentric/androidtestktx

Kotlin DSL for Espresso and UIAutomator.

androidtestktx's Issues

Connect the CI pipeline

We should set up the CI pipeline somewhere, where we'll execute all tests from the demo in order to verify that new implementations are working properly. Let's not forget to wire the testing results with the test tag in the README file.

Cover the TEXT ViewActions

Implement missing extension functions for the TEXT part of the Espresso cheat sheet.

Cover the USER PROPERTIES ViewMatchers

Implement the missing extensions for the USER PROPERTIES part of the Espresso cheat sheet, section ViewMatchers.

Acceptance criteria:

• USER PROPERTIES should be implemented for both, Espresso and UIAutomator.
• Tests in the demo app should be written for both libraries (and passing)

Deploy the library onto the Bintray

The library should be deployed on Bintray as well as JCenter.

Separate the artefacts for Espresso and UIAutomator

Espresso and UIAutomator related code should be added as a separate dependency.

Add a build version label

On top of the README file, we should have a build version tag, linked to the bintray page: https://bintray.com/bajicdusko/maven/androidtestktx

Add a test status label

On top of the README file, we should have a test status tag, showing whether the tests are passing or not.

Cover the CLICK/PRESS ViewActions

Implement the missing extensions for the CLICK/PRESS part of Espresso cheat sheet.

Acceptance criteria:

• Click/Press actions should be implemented for both, Espresso and UIAutomator.
• Tests in the demo app should be written for both libraries (and passing)

Cover the GESTURES ViewActions

Implement the missing extensions for the GESTURES part or Espresso cheat sheet.

Acceptance criteria:

• Gestures should be implemented for both, Espresso and UIAutomator.
• Tests in the demo app should be written for both libraries (and passing)

Cover the UI PROPERTIES of ViewMatchers

Implement the missing extensions for the UI PROPERTIES part of the Espresso cheat sheet, section ViewMatchers.

Acceptance criteria:

• UI PROPERTIES should be implemented for both, Espresso and UIAutomator.
• Tests in the demo app should be written for both libraries (and passing)