Let's take a look at some more fancy features:Ĭonst mockServer = require('mockttp'). That is pretty easy, but we can make this simpler & more powerful. (Want to play with this yourself? Try running a standalone version live on RunKit: ) MockServer.get('/mocked-path').thenReply(200, 'A mocked response')Įxpect(response.text).to.equal('A mocked response') It('lets you mock requests, and assert on the results', () =>

Here's a simple minimal example of all that using plain promises, Mocha, Chai & Superagent, which works out of the box in Node and modern browsers:Ĭonst superagent = require('superagent') Ĭonst mockServer = require('mockttp').getLocal() īeforeEach(() => mockServer.start(8080)) * Mock the endpoints you're interested in To run an HTTP integration test, you need to: * Write modern test code, with promises all the way down, async/await, and **strong typing** (with TypeScript) throughout * **Debug your tests easily**, with full explainability of all mock matches & misses, mock autosuggestions, and an extra detailed debug mode * **Safely mock HTTP in parallel**, with autoconfiguration of ports, mock URLs and proxy settings, for super-charged integration testing * **Mock for node & browser tests with the same code** (universal/'isomorphic' HTTP mocking) * Stub direct requests, or transparently stub requests elsewhere as an **HTTP mocking proxy** * **Test true real-world behaviour**, verifying the real requests made, and testing exactly how your whole stack will handle a response in reality * **Mock requests inside or outside your process/tab**, including subprocesses, native code, remote devices, and more * **Intercept HTTPS** too, with built-in self-signed certificate generation * **Stub server responses** and **verify HTTP requests** made by your code Based on project statistics from the GitHub repository for the npm package httptoolkit. * Write **easy, fast & reliable node.js & browser HTTP integration tests** httptoolkit/websocket-stream popularity level to be Popular. Strong typing & promises throughout, fast & safe parallel testing, and helpfulīuilt-in debuggability support all the way down. Works out of the box in node or browsers, with support for transparent proxying & HTTPS, Mockttp allows you to do accurate true integration testing, writing one set of tests that It's inflexible, limiting and inaccurate, and often unreliable & tricky to debug too. Real requests that'd be made, and only works for requests made in the same JS processs. That ties you to a specific environment, doesn't test the There's a lot of tools to do this, but typically by stubbing the HTTP functions in your **Mockttp lets you quickly & reliably test HTTP requests & responses in JavaScript, in both Node and browsers.** > _Part of (): powerful tools for building, testing & debugging HTTP(S)_

Httptoolkit github