Kotlin: Make an internal function visible for unit tests

unit-testing kotlin package-private
Jan Pomikálek picture Jan Pomikálek · Feb 28, 2016 · Viewed 20.1k times · Source

In case the tests are in a different module than the production code (which is common), what's the best way to make internal functions visible for tests?

In Java, I would have the production code and the test in the same package and make the methods-to-be-tested package-private (plus, add a @VisibleForTest annotation if the only reason for having it package-private rather than private is the test). Unfortunately, Kotlin doesn't have the concept of package-private.

Answer

Jayson Minard picture Jayson Minard · Feb 29, 2016

Classes and methods marked with internal access modifier will work from within current versions of Kotlin, Gradle and also Intellij for accessing those methods from test classes. The tools consider the main and test source paths as part of the same module.

Did you try this already? And if it failed you should report a bug since this was already reported, fixed and should be fine in any current version.

Related questions

Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0

I've got a gradle FAILURE: ..."Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0." Case description: Attached to the project codebase the next libs: APP/build.gradle //(Required) Writing and executing Unit Tests on the JUnit …

Read More
Test expected exceptions in Kotlin

In Java, the programmer can specify expected exceptions for JUnit test cases like this: @Test(expected = ArithmeticException.class) public void omg() { int blackHole = 1 / 0; } How would I do this in Kotlin? I have tried two syntax variations, but none of them …

Read More
kotlin mockk not answer found error

Hi i am trying to mock the response i get from a Single observable that gets returned from retrofit using a delegator that my presenter class calls and i am getting the following error: io.mockk.MockKException: no answer found …

Read More