Search
You can now search through our
archive
!
Please specify a keyword
-
Issue #369
When Mohammed Audhil started writing test cases, he was sure to use DI, mock server response, and it took a while to come with a fully functional flow. He shares it here step-by-step.
-
Issue #368
This is a short tutorial/intro by Peter Törnhult on how to set up and use Robolectric to create Component tests for your custom views.
-
Issue #368
Using Given When Then has helped Alistair Sykes to structure tests, write single responsibility tests and improve test coverage. Here he describes how it helps.
-
Issue #365
Barry Bryant shows how Fastlane, a tool to automate all of various repetitive tasks from building and testing to notifying our teammates and deploying to Google Play, can be integrated into your project.
-
Issue #365
Robert Konarskis believes that it is a good time to start thinking about covering your apps with automated tests, and in this post he shares his findings with you.
-
Issue #364
Jose Alcérreca shows how to write & use the Espresso testing framework's idling resources to make your UI tests fast and reliable.
-
Issue #360
Artur Dryomov shares a couple tips for speeding up your CI builds.
-
Issue #358
Performance testing is something rare that we see in nowadays application development. Great tutorial by Marcos Holgado about how to use @JankTest to detect framerate drops.
-
Issue #358
Ahmed Elshahawi gives an example of how to use JUnit & mockito
-
Issue #353
The testing team at Google introduced the Android X Test libraries, amongst which we can find ActivityScenario, a new way to test Activities and code related to them. These APIs made it to a stable version, so Roberto Orgiu shows how to use them.
-
Issue #352
In this Espresso testing tutorial, Victoria Gonda shows how to create UI tests with Espresso and how to leverage Screen Robots to make them clear and maintainable.
-
Issue #352
After years of writing and reading tests, Artur Dryomov discovered that mocking is either overused or underused; striking the right balance seems to be a complicated issue.
-
Issue #347
In this video, Nate Ebel looks at an Android Developer Option to simulate a display cutout which can make testing your cutout support easier.
-
Issue #345
Piotr Mądry shares some advanced tips on using Espresso for testing.
-
Issue #345
Architecture components are one of the most exciting things that happened to Android in the past years. But how do you effectively go about and testing this? Jeroen Mols shows you how.
-
Issue #344
In this post Josef Raska explains how to test LiveData and ViewModels effectively. He explains how to implement your own TestObserver and what to look for. Also be sure to checkout his library.
-
Issue #344
TestObserver to easily test LiveData and make assertions on them.
-
Issue #344
In this article by Alex Townsend you'll learn how to leverage a custom FragmentFactory for constructor injection using a library like Dagger. The basic idea is to improve testability by enabling Fragment testing in isolation.
-
Issue #343
In this article, Alin provides a guideline for writing a robust unit test suite so that your app can have better test coverage and reliable tests.
-
Issue #339
Learning from analyzing code is one of the greatest ways to improve your skills. Jeroen Mols brings a fun little quiz for both testing gurus as novices, with a deep dive into the how and why of awesome tests.
-
Issue #339
Pamela Hill aims to help Android developers level up their Kotlin skills, focussing on intermediate/expert language features such as coroutines, DSLs, and libraries/frameworks such as Koin for dependency injection, and Spek for testing.
-
Issue #339
Shares real-world examples of how to make testing your (Kotlin) App easier and quicker so you can have more time and more confidence in the quality of your releases.
-
Issue #339
In this mini fragment, Donn and Kaushik share some thoughts on real world testing with Android development – a favorite topic of theirs.
-
Issue #338
Arnaud Giuliani looks at using Koin, from basic dependency injection to the Android architecture's components, without forgetting the testing part
-
Issue #335
If you can’t test web, native & hybrid mobile apps in a common platform. If you can’t see test data for real devices (both on-premise & in the cloud), or if you can’t use automation frameworks/mobile tools you already have and love. It’s time to check out Kobiton.
-