StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Check out <a href="http://hackage.haskell.org/packages/archive/pipes/2.3.0/doc/html/Control-Proxy-Tutorial.html" rel="nofollow">Control.Proxy.Tutorial</a>. If you can write a Proxy wrapper around your type, then you can easily swap out the test interface and a real interface like this:</p> <pre><code>client <-< simulatedServer client <-< realServer </code></pre> <p>Edit: To answer your question in the comment, you use a <code>Server</code> to write a wrapper around your <code>simpleHTTP</code> requests:</p> <pre><code>realServer :: HStream ty => Request ty -> Server (Request ty) (Result (Response ty)) IO r realServer = foreverK $ \req -> do result <- lift $ simpleHTTP req respond result </code></pre> <p>The simulated server would look like:</p> <pre><code>simulatedServer :: (Monad m, HStream ty) => Request ty -> Server (Request ty) (Result (Response ty)) m r simulatedServer = foreverK $ \req -> do result <- lift $ simulatedRequest req respond result </code></pre> <p>And your client would look like:</p> <pre><code>client :: (Monad m, HStream ty) => () -> Client (Request ty) (Result (Response ty)) m r client () = forever $ do let req = <something> result <- request req lift $ doSomethingWith result </code></pre> <p>Then you can test the real server and fake server using:</p> <pre><code>-- Test the real server main = runSession $ client <-< realServer -- Test the fake server main = runSession $ client <-< simulatedServer </code></pre> <p>The <code>client</code> and <code>simulatedServer</code> are polymorphic in the base monad only because I don't know what base monad they would use for your testing. The only requirement is that the two things you compose have the same base monad or that at least one is polymorphic in the base monad.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload