You might be using the interceptors in lacinia-pedestal to set up the superlifter context before lacinia executes the query. In this case, your tests will need to init superlifter and pass it in to the lacinia context

Thanks. I'll give that a try. I hacked around it for now, by redeffing the resolver for those test/notebook paths, but I'll see if I can get it working correctly based on your comment.

I got it to work, but there is a bit of weirdness that maybe should be documented. Because the superlifter.lacinia/with-superlifter macro extracts the context from the nested path, [:request :superlifter], to pass along to the superlifter.api/with-superlifter macro, I ended up doing this...

(let [ctx (superlifter/start! server/superlifter-args)]
    (try
      (lacinia/execute schema query variables {:request {:superlifter ctx}})
      (finally
        (superlifter/stop! ctx))))

Glad you got it working. The weirdness being that you are passing a request into lacinia, which should be agnostic of http? Yeah, that doesn't look quite right. Could be easily fixed in superlifter to just stick it on the pedestal context rather than nesting it inside the request. This would break your tests of course, but would also have a trivial fix