Espresso SDK

[kb-kerem]

Open points:

• Environment variable handling needs to be adapted to Android best practices Handled it with buildConfig and localProperties
• Builder classes where appropriate (VisualClient, VisualCheckOptions, BuildAttributes etc.) Provided
• Use default Android http client instead of Apache's Switched to using apollo graphql client

[konraddysput]

Can we please add comments to the public API?

[omacranger]

A lot of the code here looks similar-ish to the Java client. Can none of that be imported and used here as a dependency somehow?

[kb-kerem]

A lot of the code here looks similar-ish to the Java client. Can none of that be imported and used here as a dependency somehow?

@omacranger That would be super convenient however it brings also some problems that complicates the implementation. Importing Java client brings transitive dependencies that are not compatible with Android environment, considering the target Android API (apache httpclient, graphql-java etc.). Those dependencies need to be excluded explicitly and need to be maintained for the future versions of java client if new ones show up. Also, since we are using the same package and class names for certain classes that need reimplementation (mainly VisualAPI and GraphQLClient), class/method loading problems arise in runtime. Instead of trying to fix those problems, I'd rather keep the implementations fully separate.

NVM, I've managed to get it running by changing the main package name from com.saucelabs.visual to com.saucelabs.visual.espresso. There's a clear separation of packages now so no more class/method loading problems arise.