Search
You can now search through our
archive
!
Please specify a keyword
-
Issue #163
Own and build new features on the Peak Android app
Solve challenging client performance and scaling issues
Use expert knowledge of the Android platform to help guide design and engineering decisions
Improve unit testing and continuous integration processes
-
Issue #163
Matthias Käppler's verdict for unit testing on Android: it's 2015, and it's still somewhat broken. Perhaps not as broken as it used to be, but still broken in some really fundamental ways.
-
Issue #160
The first step to rx-ify your architecture is to change the methods in the data layer so that they returned Observables. The next question is: how do you unit test this?
-
Issue #159
Whether you're looking for a new job or just testing the water, Hired is there for you. In 1 week you'll get 5+ offers from top tech companies around the US and UK. Want to learn more? Check out Hired today!
-
Issue #158
This article introduces the Tools Attributes which add metadata to resource files, facilitate manipulating, rendering, and testing layouts in Design view.
-
Issue #156
Whether you're looking for a new job or just testing the water, Hired is there for you. In 1 week you'll get 5+ offers from top tech companies around the US and UK. Want to learn more? Check out Hired today!
-
Issue #156
With the latest support library release 22.2.0, we added an @VisibleForTesting annotation to support-annotations. This annotation denotes that a class, method or field has its visibility relaxed, so that it is more widely visible than otherwise necessary to make your code more testable
-
Issue #156
Google Cloud Test Lab is an instant device testing closet, with automated reports and scaling support. Tests will run on emulators and real hardware. This is a huge step forward in getting more quality to Android apps.
-
Issue #154
App testing doesn't work if you don't use the mobile devices your customers are using. The latest Mobile Test Coverage Index report analyzes 360,000 app users and 4,000 device configurations to give the answers you need to test with confidence.
You can get the Mobile Test Coverage Index here.
-
Issue #154
This article walks you through of basic example how to use image recognition for mobile game testing and what sort of assets and test script you need for that.
-
Issue #153
RxPresso is the result of an effort to build a framework that would let developers achieve the simplicity of unit test syntax in presentation layer tests. It’s a simple way to mock data while testing and synchronise Espresso view actions with Rx pipelines.
-
Issue #152
Whether you're looking for a new job or just testing the water, Hired is there for you. In 1 week you'll get 5+ offers from top tech companies around the US and UK. Want to learn more? Check out Hired today!
-
Issue #152
Another in-depth look at getting started with the Espresso testing framework.
-
Issue #152
Chiu-Ki Chan shares how you can tell the Espresso testing framework to wait for your application by writing a custom IdlingResource.
-
Issue #151
In these slides we will learn the basics of Unit Testing and its importance and on how to write new tests and improve existing ones by reviewing some Android Github projects.
-
Issue #151
Usability testing is a technique used to help discover problems or bottle-necks in your design. But there are different types of user testing that suit different types of goals. Scripted or un-scripted? Here we’ll explain the differences between the two and how you can make the most of them.
-
Issue #151
Unit testing Android apps is hard, and sometimes it can be impossible because of the way we are encouraged to structure them. In this post, Matt Dupree outlines an alternative approach to structuring Android applications that will make it easier to unit test them.
-
Issue #150
Following the release of the Android testing support library 0.2 and Espresso-Intents this week, Stephan Linzner shares the slides for his "What’s new in Android Testing" talk which he gave at Droidcon Italy.
-
Issue #150
Tor and Chet are joined by Thomas Knych and Valera Zakharov from the Espresso team at Google. This episode is all about testing. We talk about how Espresso works, how Espresso came to be, how to use Espresso, and lots of other information about Espresso. And UI testing in general.
-
Issue #150
As long as we follow the “standard way” as seen in countless sample projects from Google, we’re going to write code that’s either difficult or impossible to unit test. This second part examines why that is.
-
Issue #149
A follow up post to "Against Android Unit Tests" explaining the difficulties of testing an Android app.
-
Issue #148
Ensure your apps run smoothly on Intel Architecture by testing through a virtual testing service. Upload your code, run tests and receive in-depth performance data and reports.
-
Issue #148
Chiu-Ki Chan shares a demo repo that shows Android instrumentation testing with Dagger 2, Espresso 2 and Mockito.
-
Issue #148
Android Studio 1.2, which is currently in beta, removes any need for third-party workarounds or custom hacks to use Robolectric as a unit testing solution. This article shows how easy it is.
-
Issue #148
Matt Dupree launches a series of articles on reframing the approach to automated testing of Android apps.
-