Hi, I need some advice about examples and their us...

# library-development

[zaleslaw]

Hi, I need some advice about examples and their usage in project infrastructure. I have 100 examples in the library that could be reused like integration tests for my library. Each example contains one main() function. I want to create 100 tests, each of them should call this main function. How to do it in Kotlin? How to call a specific main function? For example Example1.main()? It's easy in java, but I could not find a way in Kotlin.

[Iaroslav Postovalov]

What's the problem with calling the function by its FQ name?

[Big Chungus]

Import my.package.main as Main1

@Test
fun test() {
Main1()
}

[Big Chungus]

Main is just a top level function with specific reserved name and args spec. You can call it like any other top level function.

[ilya.gorbunov]

The difference of main function is that it's allowed to have several top-level such functions in one package, but in different files. This works well when these functions are used as entry points for JVM, but it's impossible to distinguish them when calling from Kotlin

[ilya.gorbunov]

So either you have to put each main in its own separate package and call it from Kotlin by fq-name or you can invoke them with Java reflection

[zaleslaw]

The problem is that I don't want to pack each example in a separate package. As I see according @ilya.gorbunov the best way here to call them from Java because it could be distinguished there with FQ including the name of the file (converted to class) where it's located.

[zaleslaw]

@Iaroslav Postovalov The problem is that FQ is not really FQ for the main functions. Unfortunately it doesn't include the underhood Java class name like (Example1Kt). Do you know how to write correct FQ if you have package with 10 examples and each of them has main entry point?

[Big Chungus]

You can leave aliases in each file where main lives

[Big Chungus]

fun main() {}
val uniqueIdentifier = ::main

[zaleslaw]

@Big Chungus sounds interesting, I wanted to avoid changes in examples for using in test infrastructure, but it could be a simple and enough clean solution, thanks

[Big Chungus]

Or even better yet, have main delegate to named fun

fun uniqueFunction() {}
fun main() = uniqueFunction()

Then use uniqueFunction in tests

[zaleslaw]

Yeah, keep in mind this variant. But I was wondered that I have no ability to specify the road to main() call in Kotlin but I could do it in Java

[Big Chungus]

Alternatively you could try

object Wrapper {
fun main(){}
}

[Iaroslav Postovalov]

Nope, @JvmStatic fun main looks much worse

[ephemient]

@JvmName("main") fun uniqueMain()?

[zaleslaw]

Hmmmm, @ephemient sounds interesting