one of the most compelling uses of Kotlin is for u...

# android

[codeslubber]

one of the most compelling uses of Kotlin is for unit tests, but after spending hours on getting Spek to work in a vanilla project generated from AS3, I need to move on, found an article about using JUnit where the tests are written in K, is that a good approach? is there a better source than this?

https://fernandocejas.com/2017/02/03/android-testing-with-kotlin/

[dalexander]

I wouldn’t try using anything other than JUnit (or something built on top of JUnit) for Android testing, I don’t know the details but there seems to be some kind of “most favored” status for JUnit on the platform.

[codeslubber]

Thanks. I am just coming to that conclusion. I am surprised that they don’t even have JUnit 5 in the AS3 templates? what on earth? and at their developer event a few years ago Google admonished devs for not writing tests!!

[codeslubber]

Make it easier if you want people to do it. They did in ios. There is zero fuss there now and the tests run at ridiculous speed..

[dalexander]

Only JUnit 4 has the “most favored framework” status.

[dalexander]

It was JUnit 3… 3 years ago maybe? There’s something that happens during the build process which makes it possible, but I don’t know the details. I think most Android developers who are interested in testing, aren’t happy about the level of support provided.

[dalexander]

(This is ignoring that in my opinion, many apps can be reduced to a series of I/O and UI operations, which makes a poor match for testing)

[codeslubber]

I agree completely with your opinion about most apps!.. but I am pretty much TDD like I cannot stand to write code without tests..

[codeslubber]

I created a new project

[codeslubber]

just took the vanilla junit and got my tests running in a few mins but then

[codeslubber]

cannot figure out how to get at assertThat … does not offer to import

[codeslubber]

and the docs say you might have to add assertions but they don’t say how.. seriously if people are not writing enough tests it’s because there are too many logical people out there… they should hang a sign like the one in Dante on the testing page…

[codeslubber]

couldn’t get assertThat to work so I just did assertEquals.. one day I will make something from a template and it will work.. or wait I should say one day someone will…

[Karolo]

Did you try manual import ? @codeslubber

[codeslubber]

yes

[codeslubber]

I got it to find assertThat

[codeslubber]

with manual import (which is like going back in time 2 decades)

[codeslubber]

but could not find the matchers

[codeslubber]

and there’s no mention of them in the docs

[codeslubber]

also

[codeslubber]

the docs show an example that I cannot see how it would compile

[codeslubber]

it has assertThat and is and no imports for either

[Karolo]

Did u imported matchers? I found one topic on sof and one person was missing sth like org.hamcrest.CoreMatchers.*

[codeslubber]

ok so yeah got it to work now using assertThat and the core matchers

[codeslubber]

thanks @Karolo

[codeslubber]

I knew about the import thing not working but did not think hamcrest was there

[codeslubber]

because it was made from the vanilla template

[codeslubber]

(must be in the junit jars.. )

[kasper.kondzielski]

Hi, we managed to use spek in android project for unit tests but we were not contented with it due to its sharing state nature. So we created our own mini spek, which you can check here: https://github.com/elpassion/MiniSpek

[kasper.kondzielski]

it’s still under development but for know it works for both android and unit tests, so I thought you might want to check it out