Writing Clean Architecture Use Cases w/ TDD | Kotlin Android Alarm App | Mockk JUnit 5

preview_player
Показать описание
Just a brief coding session where I write out some test cases to create some Use Cases using TDD (Test Driven Development). The application is an Alarm app, platform is Android, and the language is Kotlin. I talk a lot about general information on testing, Kotlin, Mockk, and how general test driven development process.

1:03 - Finishing off a test suite which I started yesterday
21:42 - Creating Test suite from scratch to implement a Use Case Stub

Looking for a comprehensive introduction to Kotlin, Android, and Programming in general? If so, consider picking up my introductory course to Programming Fundamentals with Kotlin and Android on Udemy; I don't think you'll be disappointed:
Рекомендации по теме
Комментарии
Автор

You should always write your test cases even if the implementation looks simple. The implementation can scale or get more complex in the future.

ForCeGR
Автор

Wouldn't you want to test your Use Cases to verify that it still does what you want it to? So if requirements change and the Use Case is no longer relevant, you can verify it?

Interested to hear thoughts on it.

lukeyd