I have some ktor server tests and ktor s server test harness

Question

I have some ktor server tests and ktor s server test harness involves executing the requests inside of a scope which means my verification of the responses happens there Looks something like this ```context when the server withTestApplication myServerModule context receives a request for url to something with handleRequest <http HttpMethod Post|HttpMethod Post> url to som ething should return the correct response response status shouldBe HttpStatusCode OK ``` This doesn t work though as where `should` is there isn t a coroutine scope and it complains Is there a better way to do tests like this Or would it be possible to have a non suspend version of `should`

bbaldino · Answer

I can wrap it `runBlocking` in the meantime but that feels a bit hacky

sam · Answer

are you on 4 1 1

sam · Answer

In 4 1 x we made all scopes be suspendable

bbaldino · Answer

4 1 1 yeah

sam · Answer

seems like maybe one was missed

sam · Answer

does it work if you change should to test and ShouldSpec to FunSpec

bbaldino · Answer

Well I think the scope is suspendable at some layer but I m wrapped inside this ktor test harness scope

sam · Answer

Actually I see

sam · Answer

The with is changing the receiver probably so you can t call should

sam · Answer

try to reference the context lambda in a var It might be ugly though

sam · Answer

```context when the server withTestApplication myServerModule context receives a request for url to something context gt with handleRequest <http HttpMethod Post|HttpMethod Post> url to som ething context should return the correct response response status shouldBe HttpStatusCode OK ```

LeoColman · Answer

An alternative which you probably thought of but just in case is to invert `with` and `should`

LeoColman · Answer

And having ktor context as the last inner context

bbaldino · Answer

Thanks < sam> that s not too bad

bbaldino · Answer

< LeoColman> I ve got multiple should blocks for the request so can t flip unfortunately confused

LeoColman · Answer

Yeah that s what I thought

LeoColman · Answer

I believe KTor also has a way to execute that code without using `with`

LeoColman · Answer

You can probably put ktor s receiver in a variable and operate with that inside your next scopes

bbaldino · Answer

Actually that s a good idea < LeoColman> That might be best

bbaldino · Answer

Even just saving the return of `handleRequest` rather than using `with`

bbaldino · Answer

Ah shit it s not that part which is screwing it up

bbaldino · Answer

Or at least not only that part

bbaldino · Answer

It s the top level server part

bbaldino · Answer

the `withTestApplication` lambda is a receiver

sam · Answer

Do the same trick and move the context gt up to the top scope

bbaldino · Answer

Oh wait there is a non suspending `should`

bbaldino · Answer

Oh but it doesn t take a TestContext block

sam · Answer

don t mix up should scope with the should assertion

bbaldino · Answer

Yeah I m looking at `ShouldSpecContextScope kt`

bbaldino · Answer

there are 4 shoulds there but yeah I guess the non suspend ones are for something else

bbaldino · Answer

I m also considering writing a non suspend `should` function there which just calls the suspend one inside of `runBlocking`

bbaldino · Answer

Ok I think I m gonna do that point up < sam> is it PR worthy to add that

sam · Answer

The framework shouldn t be calling runBlocking at all

bbaldino · Answer

ok

sam · Answer

``` fun should name String = TestWithConfigBuilder TestName should name testContext defaultConfig xdisabled = false fun xshould name String = TestWithConfigBuilder TestName should name testContext defaultConfig xdisabled = true ```

bbaldino · Answer

~maybe `coroutineScope` would do it~

sam · Answer

Those two are non suspend because the test is passed into the second call on those

sam · Answer

there are for `should name config `

bbaldino · Answer

gt into the second call what do you mean

bbaldino · Answer

ah

bbaldino · Answer

does `ContainerScope addTest` need to be suspend

bbaldino · Answer

Nevermind the real question is if `registerTestCase` needs to be suspend

sam · Answer

Yes because it ends up calling into the spec runners

bbaldino · Answer

Ok

sam · Answer

and that s getting in the heart of the execution of the tests which are all coroutine based

bbaldino · Answer

Hm naming the context receiver doesn t actually work since it s a receiver not an argument

bbaldino · Answer

And naming it via `context some test test ` and then doing `this test should` doesn t work either

sam · Answer

inside the context then do `val context = this`

bbaldino · Answer

That still doesn t work because it isn t within a coroutine body where I m trying to call it

bbaldino · Answer

Hmph confused

sam · Answer

```context when the server val c1 = this withTestApplication myServerModule c1 context receives a request for url to something with handleRequest <http HttpMethod Post|HttpMethod Post> url to som ething should return the correct response response status shouldBe HttpStatusCode OK ```

bbaldino · Answer

Ayyyyy tada Good idea

bbaldino · Answer

Oh shit

bbaldino · Answer

Same problem `context` has to be called within a coroutine confused

sam · Answer

wrap it in a runblocking then

sam · Answer

that s ok for your test case

bbaldino · Answer

Yeah