https://github.com/chetanvaghela457/rickymotry_mvvm_kotlin_unittesting_demo
This repository is an innovative Android application created using Kotlin and follows the principles of Clean Architecture and MVVM design pattern. The app aims to provide users with Test Cases written for the every page. It focuses on Unit Test using mockito.
https://github.com/chetanvaghela457/rickymotry_mvvm_kotlin_unittesting_demo
android-application clean-architecture dagger2 hilt hilt-dependency-injection kotlin mockito mvvm-android mvvm-architecture testing unit-testing unittest
Last synced: 3 months ago
JSON representation
This repository is an innovative Android application created using Kotlin and follows the principles of Clean Architecture and MVVM design pattern. The app aims to provide users with Test Cases written for the every page. It focuses on Unit Test using mockito.
- Host: GitHub
- URL: https://github.com/chetanvaghela457/rickymotry_mvvm_kotlin_unittesting_demo
- Owner: chetanvaghela457
- Created: 2023-07-13T04:42:39.000Z (almost 2 years ago)
- Default Branch: main
- Last Pushed: 2023-08-05T07:18:50.000Z (almost 2 years ago)
- Last Synced: 2025-01-23T23:30:19.006Z (5 months ago)
- Topics: android-application, clean-architecture, dagger2, hilt, hilt-dependency-injection, kotlin, mockito, mvvm-android, mvvm-architecture, testing, unit-testing, unittest
- Language: Kotlin
- Homepage:
- Size: 384 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# RickAndMorty App
RickAndMorty MVVM Unit Test app is built on Clean Architecture and MVVM, which shows character lists by selected locations.
App includes Unit Tests over Data, Domain and, UI layers.
# Test Cases
# App Architecture
App architecture design is an important consideration for ensuring that your apps are robust, testable, and maintainable.
Clean Architecture combines a group of practices that produce systems with the following characteristics:
- Testable
- UI-independent (the UI can easily be changed without changing the system)
- Independent of databases, frameworks, external agencies, and libraries
### Data Layer:
Data layer includes application data and business logic. Data layer contains APIs,dto(Data Transfer Objects), repositories, source, and mappers.
### Domain Layer:
Domain layer is responsible for handling business logic and sits between Ui and Data layers.Domain Layer includes usecases and entities.
### Ui Layer:
Ui layer displays application data on the screen and makes Ui ready to interact with users. It contains UI-related state and Ui logic. Ui layer includes viewmodels, fragments, activities, components, states, mappers.
## Importance of Mapping Data Between Layers
In-app, each layer has a data model on its own, and data is mapped between layers to each layer model. Using different models per layer is perfect for a clean architecture approach. If the app sticks to just one model and some situations like database modifications, adding restful apis to data source or needing a usable model for Ui, comes out the app needs to update all models. Using models per layer is a great key to creating scalable and maintainable software.
# Tech Stack & Open Source Libraries
- Minimum SDK level 21
- %100 [Kotlin](https://kotlinlang.org/) based
- [Use Cases](https://developer.android.com/topic/architecture/domain-layer)' purpose is to request data from repositories and turn them ready to use for the Ui layer.
- [Repository](https://developer.android.com/topic/architecture/data-layer) pattern is a design pattern that isolates the data layer from the rest of the app.
- [Coroutines](https://developer.android.com/kotlin/coroutines) for asynchronous programming on Android.
- [Flow](https://developer.android.com/kotlin/flow) is a type that can emit multiple values sequentially, as opposed to suspend functions that return only a single value In coroutines
- [ViewModel](https://developer.android.com/topic/libraries/architecture/viewmodel) class is a business logic or screen level state holder. It exposes state to the UI and encapsulates related business logic
- [LiveData](https://developer.android.com/topic/libraries/architecture/livedata) is an observable data holder class.
- [Lifecycle](https://developer.android.com/topic/libraries/architecture/lifecycle) is a class that holds the information about the lifecycle state of a component (like an activity or a fragment) and allows other objects to observe this state.
- [Navigation Component](https://developer.android.com/guide/navigation) refers to the interactions that allow users to navigate across, into, and back out from the different pieces of content within app
- [Preferences DataStore](https://developer.android.com/topic/libraries/architecture/datastore) is a data storage solution that allows you to store key-value pairs.
- [Retrofit](https://square.github.io/retrofit/) A type-safe HTTP client for Android and Java
- [Dagger Hilt](https://dagger.dev/hilt/) Hilt provides a standard way to incorporate Dagger dependency injection into an Android application.
- [ViewBinding](https://developer.android.com/topic/libraries/view-binding) is a feature that allows you to more easily write code that interacts with views.
- [Coil](https://coil-kt.github.io/coil/) An image loading library for Android backed by Kotlin Coroutines.
- [Extension Functions](https://kotlinlang.org/docs/extensions.html) Kotlin provides the ability to extend a class or an interface with new functionality without having to inherit from the class or use design patterns
# Unit Testing
- [MockWebServer](https://github.com/square/okhttp/tree/master/mockwebserver) A scriptable web server for testing HTTP clients
- [Mockito](https://site.mockito.org/) Mocking framework for unit tests
- [Truth](https://truth.dev/) is a library for performing assertions in tests:
- [Turbine](https://github.com/cashapp/turbine) is a small testing library for kotlinx.coroutines Flow.