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

@secondcloset/frontend-test-utils

v1.0.2

Published

Utilities for testing front-end applications

Downloads

145

Readme

@secondcloset/frontend-test-utils

Utilities for testing front-end applications

Installation

npm install @secondcloset/frontend-test-utils --save-dev

In your test suite:

import { lens, componentLens } from "@secondcloset/frontend-test-utils";

Utilities

lens

Allows to set and read value of Recoil state

const { render, result } = lens(node);

Options

  • node: RecoilState<T> - Recoil state

Returns

  • render: () => JSX.Element - render this function inside of RecoilRoot
  • result
    • set: SetterOrUpdater<T> - this functions is used to set Recoil state value
    • reset: Resetter - this function is used to reset Recoil state value
    • value: T | undefined - current value of Recoil state

Example

// usernameState.ts
export const usernameState = atom({
  key: "usernameState",
  default: "Anonymous",
});

// User.tsx
export const User = () => {
  const username = useRecoilValue(usernameState);

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

// User.test.tsx
test("renders username", () => {
  const { render: renderUsernameState, result: usernameStateLens } = lens(usernameState);

  render(
    <RecoilRoot>
      {renderUsernameState()}
      <User />
    </RecoilRoot>
  );

  let username = screen.queryByText(/anonymous/i);
  expect(username).toBeInTheDocument();

  act(() => {
    usernameStateLens.set("John Doe");
  });

  username = screen.queryByText(/john doe/i);
  expect(username).toBeInTheDocument();
});

// UsernameInput.tsx
export const UsernameInput = () => {
  const setUsername = useSetRecoilState(usernameState);

  return (
    <div>
      <input
        onChange={(e) => {
          setUsername(e.target.value);
        }}
      />
    </div>
  );
};

// UsernameInput.test.tsx
test("updates username", () => {
  const { render: renderUsernameState, result: usernameStateLens } = lens(usernameState);

  render(
    <RecoilRoot>
      {renderUsernameState()}
      <UsernameInput />
    </RecoilRoot>
  );

  const usernameInput = screen.getByRole("textbox");
  userEvent.type(usernameInput, "Michael Scott");

  expect(usernameStateLens.value).toBe("Michael Scott");
});

componentLens

Allows to read the prop values of a mocked component that have passed to it during rendering. It is also possible to call functions (usually event handlers) that have been passed as props to that component

const { props } = componentLens(ComponentMock, render?);

Options

  • componentMock: jest.MockedFunction<React.FC<T>> - mocked component
  • render: (props: PropsWithChildren<T>) => ReactNode - custom render function

Returns

  • props: { current: PropsWithChildren<T> } - component props (including children)

Notes

  • It is possible to use jest.Mock instead of jest.MockedFunction when mocking component, but you will lose type support for component props

Example

// User.tsx
interface UserProps {
  initialUsername: string;
}
export const User: React.FC<UserProps> = ({ initialUsername }) => {
  const [username, setUsername] = useState(initialUsername);

  return (
    <div>
      {username}

      <UsernameInput
        value={username}
        onChange={(value) => {
          setUsername(value);
        }}
      />
    </div>
  );
};

jest.mock("./UsernameInput");
const UsernameInputMock = UsernameInput as jest.MockedFunction<typeof UsernameInput>;

test("updates username", () => {
  const { props: UsernameInputProps } = componentLens(
    UsernameInputMock,
    ({ children }) => <div>{children}</div>
  ));

  render(<User initialUsername="Anonymous" />);

  expect(UsernameInputProps.current).toMatchObject({ value: "Anonymous" });

  act(() => {
    UsernameInputProps.current.onChange("John Doe");
  });

  expect(UsernameInputProps.current).toMatchObject({ value: "John Doe" });
});