How do you maintain code quality in your projects…

Use of static analyzers: I use tools like Detekt and ktlint for automatic detection of potential errors, style violations, and code smells.
Code Reviews: I participate in peer code review processes. This helps identify errors early, share knowledge, and ensure consistency.
Unit and Integration Tests: I write tests for key components and business logic to ensure their correct operation and to prevent regressions during changes.
DI (Dependency Injection): I use DI (e.g., Dagger/Hilt, Koin) to improve testability, modularity, and dependency management.
SOLID Principles: I strive to follow SOLID principles to build flexible, maintainable, and extendable architecture.
Continuous Integration/Continuous Deployment (CI/CD): I set up CI/CD pipelines (Jenkins, GitLab CI, GitHub Actions) for automatic testing, static analysis, and building after each commit.
Consistent Code Style: I adhere to a unified coding style in the project, using formatters and style guides (Kotlin Style Guide, Android Style Guide).
Clear and Concise Naming: I use understandable and informative names for variables, functions, and classes.
Proper Documentation: I add comments where necessary to explain complex logic or non-obvious decisions. KDoc for public APIs.
Architectural Patterns: I apply suitable architectural patterns (MVVM, MVI) to structure the project and separate responsibilities.
Immutable Data Structures: Whenever possible, I use immutable data structures to reduce the likelihood of errors related to state changes.

// Example of a unit test with Mockito and JUnit 4
@Test
fun testDataLoadingSuccess() {
    // Arrange
    val expectedData = listOf("item1", "item2")
    `when`(mockRepository.getData()).thenReturn(Single.just(expectedData))

    // Act
    viewModel.loadData()

    // Assert
    verify(mockRepository).getData()
    assertEquals(expectedData, viewModel.data.value)
    assertEquals(false, viewModel.isLoading.value)
}

How do you maintain code quality in your projects?