does anybody know if mockk v1.11.0 supports mockin...

# announcements

[Peter Ertl]

does anybody know if mockk v1.11.0 supports mocking inline value classes? it seems it does not…

[christophsturm]

try in #C9EJFT6DB . but i wonder how mocking inline classes should even work.

[Peter Ertl]

ok cool …

[Peter Ertl]

I think mockk will have to mock the inline value (e.g. an embedded string) instead

[Peter Ertl]

@JvmInline value class CustomerName(val name: String)

should probably generate a mock that operates on String

[Emil Kantis]

Is there any value in mocking value classes? Have you added behaviour to it?

[Peter Ertl]

no, but I want to mock an interface call that returns a value class … and this does not seem to work

[Peter Ertl]

I got an answer on #C9EJFT6DB: https://github.com/mockk/mockk/issues/485

[Emil Kantis]

Ahh, that makes sense

[Peter Ertl]

this is the related issue

[Peter Ertl]

it’s currently unresolved

[Emil Kantis]

Not even this is possible?

val mock = mockk<SomeInterface>()

every { mock.getCustomerName() } returns CustomerName("Some name")

[Peter Ertl]

based on my current experiments I would say: “no”

[Peter Ertl]

this narrows the usage of value classes in my case significantly

[Peter Ertl]

since testing is not optional

[Peter Ertl]

I get a error message like “CustomerName cannot be cast to java.lang.String”

[Peter Ertl]

I still do experiments and I will update

[Youssef Shoaib [MOD]]

Could you try maybe doing a returns with the underlying datatype directly? E.g. every { mock.getCustomerName() } returns "Some name"