A modern programming language that makes developers happier.

kotlinlang

Does any have experience using `Mockk` I am trying to mock the following function ```fun &lt;T&gt; openAndCloseSession(handler: (Session) -&gt; T): T {
    val session = HibernateUtil.sessionFactory.openSession()
    val res = handler(session)
    if (session.isOpen) {
        session.close()
    } else {
        println("[WARNING]: session closed by handler function: ${handler::class.java.enclosingMethod}, please consider omitting manually closing the session in the handler as it will be closed automatically at the end of the call")
    }
    return res
}``` I want the mock to just call the provided `handler` (which I have mocked too). This is where I am currently at ```val session: Session = mockk()
every { openAndCloseSession&lt;Any&gt;(any()) } answers {firstArg&lt;(Session) -&gt; Any&gt;().invoke(session)}``` Sadly this doesn't work.

Can you clarify - are you mocking `handler` or this entire function?

My problem was the fact that I was mocking a top level/static function and I hadn't called `mockkStatic(..)`.

And to answer your question, I was mocking both but my question was about mocking the function itself (I had already mocked the handler).

This is where my confusion stems from - if you’re mocking the function, where does the handler come into the picture?

I have a REST endpoint which calls `openAndCloseSession` to create a new Hibernate session which will remain open within the handler in which an action is performed (usually a DAO function) and returns the results of the handler. I just want to test my *endpoint*, I mocked the (DAO) functions that my endpoints call, I wanted to skip the creation of the Hibernate session and the mocked function to just call the handler immediately as the handler is mocked anyway. I hope it makes sense :sweat_smile:

For purely testing your endpoint, it might be better to have that call something that isn’t related to hibernate/daos’/etc.  Just have it work on an interface that performs the action and mock that instead.  Alot of this pain will then go away

You mean I should alter my actual endpoint or my test? I don't think I quite understand.

I assume your endpoint has your DAO injected into it?

It might help if you just show your endpoint code

```
@Path(PersonPaths.ROOT)
@Produces(MediaType.APPLICATION_JSON)
actual class PersonEndpoint : Endpoint() {

    @GET
    @Path(PersonPaths.GET_BY_ID)
    actual suspend fun getById(@PathParam("id") id: Long): PersonDTO = openAndCloseSession {
        val genericDaoImpl = GenericDaoImpl&lt;Person, Long&gt;(Person::class.java, it)
        genericDaoImpl.load(id)
    }?.dto ?: throw WebApplicationException(Response.Status.NOT_FOUND)

    @GET
    actual suspend fun getAll(): List&lt;PersonDTO&gt; = openAndCloseSession {
        val genericDaoImpl = GenericDaoImpl&lt;Person, Long&gt;(Person::class.java, it)
        genericDaoImpl.loadAll()
    }.map { it.dto }

    @GET
    @Path(PersonPaths.RESULTS_LIST_PATH)
    actual suspend fun getAllResultsList(): ResultsList&lt;PersonDTO&gt; = ResultsList(openAndCloseSession {
        val genericDaoImpl = GenericDaoImpl&lt;Person, Long&gt;(Person::class.java, it)
        genericDaoImpl.loadAll()
    }.map { it.dto })


    @POST
    @Status(201)
    actual suspend fun create(personDTO: PersonDTO): Long = openAndCloseSession {
        val genericDaoImpl = GenericDaoImpl&lt;Person, Long&gt;(Person::class.java, it)
        genericDaoImpl.save(personDTO.entity)
    }

}
```