Search
You can now search through our
archive
!
Please specify a keyword
-
Issue #91
A pure Gradle port of the Espresso testing utility for Android by Jake Wharton
-
Issue #84
Here's part two of Daniel Lew's series on Android testing. This time, he's going to wade into the huge number of functional testing frameworks that exist and discuss the best ones.
-
Issue #84
Almost 3 months have passed since the launch of Espresso testing framework for Android; time flies when you’re doing UI testing. We are excited to share a new version 1.1 with you.
-
Issue #82
Matt Swanson has published a nice little blog post on how to test tricky things like http requests to an API. He uses Retrofit for the REST calls and Mockito to mock the results.
-
Issue #80
Ravindra Kumar has created a sample android starter project to demonstrate the integration of the following tools:
Automation: Gradle
Testing: Android Testing Framework, Robotium, Roboelectric (JUnit, Instrumentation)
Continuous Integration: TravisCI
-
Issue #80
Join AppThwack's Trent Peterson as he demystifies Android testing with a review of automation strategy and testing tools.
-
Issue #81
An in depth article describing an automated User Acceptance Testing scenario using Gradle.
-
Issue #78
If you’re developing in Android Studio and using the Gradle build system, this guide will help you get your Test environment using JUnit and Robolectric up and running in a few easy steps.
-
Issue #76
Pascal Cans from Genymotion shows how you can already integrate their emulator with Jenkins in order to automate your Android unit tests.
-
Issue #76
Amazon added to the list of free mobile services we offer across platforms: Analytics is a fast new service, simple to understand and integrate, that shows customer engagement at a glance; while A/B Testing has been expanded to support iOS and Android in addition to Fire OS.
-
Issue #75
So depending on your environment it's kind of a PITA to test Google Cloud Messaging on an actual device. Wouldn't it be nice if you could just test the code locally that would receive those magical GCM messages? You can and this post by Nicholas Pike explains how.
-
Issue #72
The Robolectric testing framework has been updated to v2.2 and brings several useful changes.
-
Issue #71
There is a real problem testing web pages across multiple devices and the browsers that run on them. The best solutions today are to either enter a url to a tool to manage the devices or use applications across the devices, keeping them open and testing in a WebView.
This project is a Virtual Device Lab. It allows you to quickly launch url's across all of a configured devices in an instant, selecting which browser to launch.
This is still in early stages of development, which means you can probably expect things to break, but we'd love help, bugs and feature requests.
-
Issue #67
AppThwack rolls out Android app testing with Android Studio and Gradle. It lets you easily run your unit tests on their set of mobile devices direct from Studio or your Gradle build.
-
Issue #90
Chuck Greb at aweber describes how they implement unit testing around the open source Picasso image downloading library.
-
Issue #64
Selendroid is a test automation framework which drives of the UI of Android native and hybrid applications (apps). Tests are written using the Selenium 2 client API. Selendroid can be used on emulators and real devices and can be integrated as a node into the Selenium Grid for scaling and parallel testing.
-
Issue #62
Testing your APIs automatically can be painfull. This library makes it possible to write fast, reliable unit tests for HTTP clients. Like object mocking frameworks, it allows you to script mock responses, exercise them, and then review the recorded requests.
-