Allure Android implementation

[kamildziadek]

New allure android implementation. All of the features of the original allure-android were migrated, with small changes that make the API more robust.

Content:

• Migrating Rules
• Migrating LogcatListener
• Implementing screenshot taking
  • implementing allureScreenshot for taking screenshots and attaching them to test results
  • using UiAutomation for taking screenshot in instrumentation tests and logging an exception in Robolectric tests
  • allowing for specifying the quality of the image
• Defining lifecycle and runners
  • defining runners that setup the lifecycle, listeners & required permissions
  • adding class runner
  • adding instrumentation runners
  • creating AllureAndroidLifecycle that uses appropriate results directory for different test types (device or robolectric)
  • adding logic for resolving the target directory
  • opening AllureLifecycle.kt
  • adding documentation
  • adding utility functions that are not exposed as an API
• Fixing NPE in FileSystemResultsWriter.kt Fixing AllureAndroidJUnit4 adding multiple listener in instrumentation tests
  • RCA: android instrumentation runner shares the RunNotifier between class runners, which results in the allure listener being added in each class runner (that leads to duplicated results)
  • FIX:
  • adding listener only once, when the AllureAndroidLifecycle has not yet been defined as default Allure.lifecycle
  • using default lifecycle for robolectric tests
  • changing AllureAndroidLifecycle.kt to be used only for device tests
  • adding documentation

Note: PR with sample usage and support for the updated target API to follow`

[kamildziadek]

This PR was made using minSdk 21 & targetSdk 28. I am resolving the issues with the compatibility to minSdk 15

[kamildziadek]

This PR was made using minSdk 21 & targetSdk 28. I am resolving the issues with the compatibility to minSdk 15

Compatibility issues resolved.

I just want to flag a couple of issues:

• We can't easily test it on API 15 as the image is no longer available for download in Android Studio
• I have noticed some runtime issues on older APIs that require further investigation
• All of the rules are only working since API 18, as they require the usage of ui-automator (safety checks & documentation has been put in place, but the rules may be a bit confusing the library users).

Considering this, I would say that it's worth increasing the min API to at least API 18 (98.4% of devices). This will help minimize the unexpected issues and make the road easier moving forward. The perfect solution would be to raise it up to API 21 (94.1% of users) as it's very stable API and I am quite confident all of the features work fine on this version.

What do you think about that @Badya, @viclovsky

[viclovsky]

This PR was made using minSdk 21 & targetSdk 28. I am resolving the issues with the compatibility to minSdk 15

Compatibility issues resolved.

I just want to flag a couple of issues:

* We can't easily test it on API 15 as the image is no longer available for download in Android Studio

* I have noticed some runtime issues on older APIs that require further investigation

* All of the rules are only working since API 18, as they require the usage of **ui-automator** (safety checks & documentation has been put in place, but the rules may be a bit confusing the library users).

Considering this, I would say that it's worth increasing the min API to at least API 18 (98.4% of devices). This will help minimize the unexpected issues and make the road easier moving forward. The perfect solution would be to raise it up to API 21 (94.1% of users) as it's very stable API and I am quite confident all of the features work fine on this version.

What do you think about that @Badya, @viclovsky

I have talked with other guys who uses allure-android library and we think that increasing the version won't be a big problem: most of the users has already increase the version. If user really need old version — it is possible to use old version of allure-android. Therefore, let's up the version smoothly: up to 18th (21th might be in future, when it will be necessary, for instance, on migrating to 29th API target version )