Sounds good right? Let’s write some code then… Getting our hands dirtyīasically, the idea is to showcase how we can test our android applications using Kotlin, so as a first step we need to setup and prepare our environment by adding Kotlin dependencies in our adle file:Ĭlass GetUserDetailsTest Espresso Acceptance (UI?) Tests
This way, we can give it a try without affecting our main application under any circumstances, and at the same time we get the excitement of a modern and already mature language, plus some training for us and our team in preparation for the big change. We have an android codebase in our old and lovely(?) Java, and we would love to introduce this awesome language gradually, so why not starting with tests? Interoperability between Kotlin and Java works almost perfect. Functions and properties are first-class citizens. Straight to the point without a lot of wiring. You can express whatever you want in a shorter way (Java is verbose). The less code you write, the fewer mistakes you make. Kotlin Programming Languageīefore starting I will just mention and give a quick summary of the main benefits of this “young?” and modern programming language: Also, I’m not going to get into details on what Kotlin offers since there is people out there doing a great job (especial mention to my friend Antonio Leiva). This is not a new topic actually, especially since Kotlin is gaining terrain in the world of programming languages in general, and especially on Android. “We should never talk about production code and testing separately, testing should be implicit when writing code as part of our solution.” This should be a good starting point towards a full migration.
In this post we will walk through how we can take advantage of the Kotlin Programming Language by introducing it in our codebase without affecting production code, in this case testing.
0 kommentar(er)
