Is there a way to setup `RequestContext` for unit ...

# http4k

[Ben Tilford]

Is there a way to setup RequestContext for unit tests that are using a mocked request?

[James Richardson]

Why would you use a mocked request? One of the main design goals appears to be that mocks are not necessary for testing anything with http4k, just use a real request.

myhandler(Request(GET, Uri.of("/path")).body("whatever"))

[s4nchez]

Precisely. Requests/Responses are values and not expected to be mocked.

[Ben Tilford]

Working with existing code

[Ben Tilford]

For a test that does depend on the request context do you run the full application then?

[Ben Tilford]

(ahh see the answer in the 1st response)

[s4nchez]

Most http4k applications are composed in such way that you can pick a part of it (http handler + key filters) and test that without much need for mocking.

[s4nchez]

I appreciate that’s not the usual style a lot of people are used to though.

[Ben Tilford]

Yeah, having taken a break from java and done Node for a couple years the pattern makes sense. Not how the codebase I inherited did things though.

[Ben Tilford]

I didn’t realize the request object was so lightweight though

[s4nchez]

not as lightweight as the core of http4k 😉 https://github.com/http4k/http4k/blob/master/http4k-core/src/main/kotlin/org/http4k/core/Http4k.kt

[dave]

It's practically obese by comparison 😂

[Ben Tilford]

What is needed to create the RequestContext during tests?

[Ben Tilford]

a: use the same context 😆