Anton Malinski

@anas-baadshah Please close this if the issue was resolved since the problem was due to apk corruption

@folkyatina if we use regex in the name - it might happen that you store multiple versions of the file in the folder and we will be unable to detect...

Since both of these parameters exist for all vendor implementations, the name would have to be consistent with the current notation, e.g. `--application-package` and `--test-application-package`. Ideally this would be generated...

Maybe we can write up another [PropertySource](https://github.com/sksamuel/hoplite/blob/0d852995d0893c1fa565ccee32192ebe8fafa747/hoplite-core/src/main/kotlin/com/sksamuel/hoplite/PropertySource.kt) to supply stuff from the command line arguments

@folkyatina another feature that you can find useful that's already in marathon is env substitution in the YAML, e.g.: ```yaml name: "sample-app tests" outputDir: "build/reports/marathon" vendorConfiguration: type: "Android" applicationApk: ${MARATHON_APP_APK}...

@Unlimity do you mean something like [this](https://github.com/junit-team/junit4/wiki/aggregating-tests-in-suites)?

At this moment `dex-test-parser` is not aware of `@RunWith(Suite.class)` at all. This could be a feature proposal to that project. Could you please create test for the sample app in...

@carlosrivin unfortunately this doesn't exist, but using an annotation on tests and filtering based on that annotation is the best approximation for suite behaviour

We need to add some information about this in the docs The options is not implemented in #265 which will be merged with #238

@alex-apriamashvili I've provided a run configuration that takes care of this setup in dev experience in #269. This should help to get everyone into the development loop much faster.