npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@apto-payments/test-server

v0.0.12

Published

Wrapper over msw to generate stubs on jest environments

Downloads

542

Readme

@apto-payments/test-server

Testing utility to be used together with jest and msw.

Getting started

Installation

Install @apto-payments/test-server as a dev dependency.

npm i -D @apto-payments/test-server @apto-payments/test-server-matchers

You might need to install the peer-dependencies yourself.

npm i -D jest msw

Configuration

Edit your jest setup files to configure the test server.

Usually this file is named setupTests.ts, you just need to add 3 steps:

  • Start the server when testing starts.
  • Close the server when testing ends.
  • Reset the server after each test to ensure a clean status.
// setupTests.ts
import server from "@apto-payments/test-server";
// (Recommended but optional) include the extended matchers
import '@apto-payments/test-server-matchers';

/**
 * Start the test-server at the beginning
 */
beforeAll(() => {
  server.listen({ onUnhandledRequest: "warn" });
});

/**
 * Reset every test-server handler after each test
 */
afterEach(() => {
  server.resetHandlers();
});

/**
 * Close the server once tests are finished
 */
afterAll(() => server.close());

Usage

Use this library to stub responses from the server while keeping your tests as deep as possible

import mockServer from "@apto-payments/test-server";
import { render, screen, waitFor } from "@testing-library/react";
import { useEffect, useState } from "react";

it("should stub the given server requests", async () => {
  const spy1 = mockServer.stubJSONResponse(
    method: "get",
    path: "*/foo/bar",
    response: { data: "hello" },
    status: 200,
  });
  const spy2 = mockServer.stubJSONResponse(
    method: "get",
    path: "*/foo/baz",
    response: { data: "world" },
    status: 200,
  });

  const res1 = await fetch("/foo/bar").then((res) => res.json());
  const res2 = await fetch("/foo/baz").then((res) => res.json());

  // We can assert on the returned spies
  expect(spy1).toHaveBeenCalledWith(
    expect.objectContaining({ method: "GET" }),
  );
  expect(spy2).toHaveBeenCalledWith(
    expect.objectContaining({ method: "GET" }),
  );

  // Optionally we can use the custom matchers 
  expect(spy1).toHaveBeenCalledWithUrl("/foo/bar", { exact: false });

  // The responses are the ones given by the test server
  expect(res1.data).toBe("hello");
  expect(res2.data).toBe("world");
});
it("should work fine with a react Element", () => {
  function DummyComponent() {
    const [serverResponse, setServerResponse] = useState();

    useEffect(() => {
      fetch("/some/url")
        .then((res) => res.json())
        .then(setServerResponse);
    }, []);

    if (!setServerResponse) {
      return <div>Loading</div>;
    }

    return <div>{serverResponse}</div>;
  }

  mockServer.stubJSONResponse({
    method: "get",
    path: "*/some/url",
    response: "This is the response from the server",
    status: 200,
  });

  render(<DummyComponent />);

  return waitFor(() => {
    expect(
      screen.getByText("This is the response from the server")
    ).toBeVisible();
  });
});