Skip to content

Latest commit

 

History

History
147 lines (100 loc) · 6.55 KB

README.md

File metadata and controls

147 lines (100 loc) · 6.55 KB
Raw

Android Testing

Jan 5th 2022

By peteHack

Open source shoppingList application demonstrating how to use different libraries to test android components in Jetpack. unit tests, integration tests, ui tests for:

  • Testing Room
  • Testing ViewModels
  • Creating fake repository and Test doubles
  • Testing Navigation with Mockito and Espresso
  • Testing with dagger hilt & retrofit
  • Testing APIs using mock web server
  • Testing fragments with dagger hilt

Prerequisite

minSdkVersion -> 21

Gradle build system

Head over to the Pixabay api and get your own API-KEY as well.

TOC

Architecture

Implemented using Clean Architecture

The application is built using MVVM architecture, the following diagram shows the structure of this project with 3 layers:



Communication between layers

  1. UI calls method from ViewModel.
  2. ViewModel executes methods called from repository .
  3. Repository returns data from a Data Source (Local or Remote).
  4. Information flows back to the UI where UI observes LiveData Object to display the list of added shopping Items.

The App is not organized into multiple modules but follows the same principles of MVVM architecture.

The presentation layer handles the UI work with the logic contained in the ViewModel. The UI uses a LiveData object from the ViewModel and observes it using the Observer Pattern. A ListAdapter handles the actual displaying of the shoppingItems. Data over the network is retrieved using retrofit and coroutines to handle background work asynchronously. Additionally, note that the ViewModel uses the viewModelScope to launch the coroutines while Fragments use the viewLifeCycleOwner to observe data. The data layer uses the recommended Repository Pattern to make the network calls and store the data using Room DB.

Libraries Used

This app will make use of the following libraries:

  • Jetpack🚀

    Android Components Dependencies

    • ViewModel - Manage UI data to survive configuration changes and is lifecycle-aware
    • Data Binding - Declaratively bind observable data to UI elements
    • Navigation - Handle everything needed for in-app navigation
    • Room DB - Fluent SQLite database access
    • LiveData - Notify views when underlying database changes

    Testing Dependencies

    • Espresso - Use Espresso to write concise, beautiful, and reliable Android UI tests.
    • Mockito - Mockito is a popular open source framework for mocking objects in software test.
    • Robolectric - Robolectric is a framework that brings fast and reliable unit tests to Android. Tests run inside the JVM
    • Hamcrest - A framework that assists writing software tests in the Java programming language. It supports creating customized assertion matchers
    • Google Truth Library - Truth makes your test assertions and failure messages more readable.
    • Junit - JUnit is a unit testing framework for the Java programming language.
    • MockWebServer - Testing API endpoints
    • Retrofit - type safe http client with coroutines support
    • Gson - A Java serialization/deserialization library to convert Java Objects into JSON and back
    • Hilt - A fast dependency injector for Android and Java.
    • okhttp-logging-interceptor - logging HTTP request related data.
    • kotlinx.coroutines - Library Support for coroutines
    • Material Design - build awesome beautiful UIs.🔥🔥
    • Glide - Hassle-free image loading
    • Timber - A logger with a small, extensible API which provides utility on top of Android's normal Log class.

Extras

Known Bugs

  • The project is currently being maintained any. Contributions are most welcome if you would like to add more modules to the project, you can reach me through my Contacts below.
  • Thanks for understanding.

CI-Pipeline

Github Actions CI is used for Continuous Integration every time an update is made to the repo. The configuration is in the .develop.yml .master.yml .branch.yml*** files

Code Analysis and test coverage

This code uses Codacy for analysing the quality of the code, which is always going to be > B :)

  MIT License
  
  Copyright (c) 2019 PeteHack
  
  Permission is hereby granted, free of charge, to any person obtaining a copy
  of this software and associated documentation files (the "Software"), to deal
  in the Software without restriction, including without limitation the rights
  to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
  copies of the Software, and to permit persons to whom the Software is
  furnished to do so, subject to the following conditions:
  
  The above copyright notice and this permission notice shall be included in all
  copies or substantial portions of the Software.
  
  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
  IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
  FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
  AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
  LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
  OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
  SOFTWARE.

Contacts

You can reach me via my personal email pwachira900@gmail.com or my website for contibutions or reuse