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

taro-testing-library

v1.1.0

Published

Simple and complete taro.js testing utilities that encourage good testing practices.

Downloads

48

Readme

taro-testing-library

Simple and complete taro.js testing utilities that encourage good testing practices.

Actions Status NPM license codecov

Install

// use yarn
yarn add taro-testing-library -D
// use npm
npm install taro-testing-library -D

Usage

set preset in your jest config file

{
  "preset": "taro-testing-library"
}

API

API

render

  • render(Component, { container, target }) => { container, unmount, rerender }: render method to mount a component

    • container: The HTML element the component is mounted into.

      default : document.body

    • target: The HTML element the component is mounted.

      default : container.appendChild(document.createElement('div'))

Result

  • container: container
  • component: created Taro.js component
  • rerender(Component): method of rerender component
  • unmount(): method of unmount component
  • debug(): method of log current dom
  • ...queries: Returns all query functions that are binded to the target.

renderToString

renderToString(Component) => string: export from nerv-server, you can use it to match snapshot

cleanup

Unmounts the component from the container and destroys the container.

cleanup() is called after each test automatically by default if the testing framework you're using supports the afterEach global (like mocha, Jest, and Jasmine).

However, you may choose to skip the auto cleanup by setting the TTL_SKIP_AUTO_CLEANUP env variable to 'true'.

To make this even easier, you can also simply import taro-testing-library/dont-cleanup-after-each which will do the same thing.

Demo

Component

import Taro, { useState } from '@tarojs/taro';
import { Text } from '@tarojs/components';

const Counter = (props) => {
  const { initial = 1 } = props;
  const [count, setCount] = useState(initial)
  return (
    <Text onClick={() => {setCount(count+1)}} className="number">
      {count}
    </Text>
  );
};

Test

import Taro from '@tarojs/taro';
import { act, render } from 'taro-testing-library';

test('should render component', () => {
  const { container } = render(<Counter />);
  const $number = container.querySelector('.number');
  expect($number.innerHTML).toEqual('1');
});

test('should rerender when trigger setState hooks', () => {
  const { container } = render(<Counter />);
  const $number = container.querySelector('.number');
  act(() => {
    $number.click()
  })
  expect($number.innerHTML).toEqual(`2`);
});

it('should support snapshot', () => {
  const component = renderToString(<div>component without state</div>);
  expect(component).toMatchSnapshot();
})