Displaying 1 to 7 from 7 results

UltimateAndroidReference - :rocket: Ultimate Android Reference - Your Road to Become a Better Android Developer

  •    Java

The goal of this project is to provide a hand-picked collection of Android libraries, tools, open-source projects, books, blogs, tutorials - you name it. This project will try to showcase only the best, most popular and well-tested resources that you will actually need and find useful rather than overwhelming you with a plethora of low-quality ones.

android-testing-guide - [Examples] Complete reference for Android Testing with examples.

  •    Java

Complete reference for Android Testing with examples. A unit test generally exercises the functionality of the smallest possible unit of code (which could be a method, class, or component) in a repeatable way.

requestmatcher - A simple and powerful way for making programatic assertions in your fake API

  •    Java

A simple and powerful way for making assertions in your mocked API. To properly test an Android application we must isolate all the external dependencies that we can't control. Normally, in a client/server application, this boils down to the API calls.




android-tests - Examples of Android tests.

  •    Java

Collection of Android app tests. Each folders are pairs of sample app codes and test codes. Test with Android ARM EABI emulator executed on Docker.

ui-testing

  •    Kotlin

The purpose of the project is to demonstrate the approach of testing the UI in Android app, by using espresso. The project has a very simple login screen, and based on the input it has to show an error, or open the main application screen. The key point of this project is to demonstrate the approach for getting a rock-solid UI tests that would run on any environment, without any external dependencies. Traditionally, there were different approaches for mocking a rest service that would run on the same machine with the emulator, so the app would make the real calls. In this example, the test doubles are created and kept in the source code, so the app would not need any external dependencies for running the UI tests. Furthermore, the replies are very fast so there is no need for any idling resources. The idea is to focus on the UI, because the initial intention is to test the UI, not the actual calls. At the beginning, it's very important to note that the project has 2 flavors: mock and prod. The reason behind is to separate the data source. The production data source implementation would make the real work (calls to sever, etc), while the mock implementation would return mocked replies (aka test-doubles) based on the input. This could have been done in many different ways (using dagger for instance), but the intention here is to achieve the goal with as little dependencies as possible, so it will be very simple to be understood.

rules4android - A collection of JUnit 4 Rules for Android Developers 🔬

  •    Kotlin

This repo contains the source code related to this article: Don't be lazy, use @Rules. rules4android is distributed through JCenter. To use it you need to add the following Gradle dependency to your android app gradle file (NOT the root file).






We have large collection of open source products. Follow the tags from Tag Cloud >>


Open source products are scattered around the web. Please provide information about the open source projects you own / you use. Add Projects.