I’m trying to mock an interface that has methods using the RaiseDSL approach, however, the mocking p...

# arrow

[Kev]

I’m trying to mock an interface that has methods using the RaiseDSL approach, however, the mocking part looks terrible and is probably wrong. What’s a more elegant approach to doing this? I don’t want to have to wrap my whenever parameter in an either, and then also have to turn the returning option into an either also.

I included the method signature as a comment within the snippet.

// context(Raise<Error>) getScopedMethod(value: String): Option<Foo>
      val mocked = mock<SomeScope> {
        whenever(either { it.getScopedMethod(any()) }).thenReturn(Foo("foo").some().right())
      }

[Riccardo Cardin]

I asked the same question once: https://kotlinlang.slack.com/archives/C5UPMM0A0/p1697275122862069

[simon.vergauwen]

I think it's time we form an official answer about this on the website. Are some people up for collaborating on this? cc\\ @CLOVIS @Olaf Gottschalk

[simon.vergauwen]

I think this would also fit in perfectly with the FAQ @Kev

[CLOVIS]

I'm up for it 🙂 Though I wouldn't recommend mocks

[Kev]

@simon.vergauwen give your talk on how to effectively do mocking using context receivers /s

[Riccardo Cardin]

I guess the best way to mocking them is not to use mocking at all 😜

[simon.vergauwen]

Teaching people FP, and not using mocks? I'm going to leave that to RockTheJvm 😂 😉

[Riccardo Cardin]

We’ll keep the topic into consideration for next articles 😜

[simon.vergauwen]

If you ever need someone to review something feel free to reach out 😉

[Riccardo Cardin]

cc @Daniel Ciocirlan

[Daniel Ciocirlan]

Would be much appreciated @simon.vergauwen! Will reach out when ready