Explore >> Select a destination
|
You are here 
|
mustafaali.net | ||
| | | | |
wittchen.io
|
|
| | | | | Introduction Some time ago, Ive written an article about Test coverage report for Android application. It got some interest (many comments below article and many visits according to Google Analytics), so I decided to refresh this topic. Previously, Ive written instrumentation unit tests, which needed to be executed on a real device or an emulator. Its a good approach when you want to test functionalities strongly connected with the device. E. | |
| | | | |
jonathanbayless.com
|
|
| | | | | The blog of Jonathan Bayless | |
| | | | |
andreabergia.com
|
|
| | | | | In this short series, we are going to dig a bit in how one writes a gradle plugin. Our plugins won't do anything useful except some println; however I hope to manage to explain some concept and to save you some time in case you have to write one. The source code for this tutorial is available on github at https://github.com/andreabergia/sample-gradle-plugin. Our first plugin Link to heading The repository is split in two projects: gradleplugin and usage. Quite obviously, gradleplugin defines our plugin, ... | |
| | | | |
blog.blundellapps.co.uk
|
|
| | | This tutorial will show you how you can architect your Android Things applications to make testing much easier. This involves two types of testing: unit and vendor testing. Google has just announced the amazing Android Things. This gives the Internet of Things (IoT) a real jump start with the availability of the Android ecosystem and | ||
