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

@nightwatch/react

v3.1.1

Published

Nightwatch plugin which adds support for React component testing using the Vite dev server. Requires Nightwatch 2.0+

Downloads

2,069

Readme

@nightwatch/react

Build Status version Discord MIT License

Official Nightwatch plugin which adds component testing support for React apps. It uses the Vite dev server under the hood and vite-plugin-nightwatch. Requires Nightwatch 2.4+

npm install @nightwatch/react

Usage:

Update your Nightwatch configuration and add the plugin to the list:

module.exports = {
  plugins: ['@nightwatch/react']
  
  // other nightwatch settings...
}

Already using Vite in your project?

If you already have a Vite project, then the @nightwatch/react plugin will try to use the existing vite.config.js or vite.config.ts, if either one is found.

Check the vite-plugin-nightwatch project for more configuration options.

Update the vite.config.js and add the vite-plugin-nightwatch plugin:

// vite.config.js

import nightwatchPlugin from 'vite-plugin-nightwatch'

export default {
  plugins: [
    // ... other plugins, such as vue() or react()
    nightwatchPlugin()
  ]
})

Configuration

We’ve designed the @nightwatch/react plugin to work with sensible configuration defaults, but in some more advanced scenarios you may need to change some of the config options.

Vite dev server

By default, Nightwatch will attempt to start the Vite dev server automatically. You can disable that by adding the below in your nightwatch.conf.js file, under the vite_dev_server dictionary.

This is common to other component testing plugins that are based on Vite, such as the @nightwatch/vue plugin.

// nightwatch.conf.js

module.exports = {
  plugins: ['@nightwatch/react'],
  vite_dev_server: {
    start_vite: true,
    port: 5173
  }
}

Plugin options

The plugin accepts a few config options which can be set when working with an existing vite.config.js file in the project.

- renderPage

Specify the path to a custom test renderer to be used. A default renderer is included in the package, but this option can overwrite that value.

// vite.config.js

export default {
  plugins: [
    // ... other plugins, such as vue() or react()
    nightwatchPlugin({
      renderPage: './src/test_renderer.html'
    })
  ]
}

API Commands:

This plugin includes a few Nightwatch commands which can be used while writing React component tests.

- browser.mountComponent(componentPath, [props], [callback]):

Parameters:

  • componentPath – location of the component file (.jsx) to be mounted
  • props – properties to be passed to the React component, this will be serialized to JSON; an inline string can be also used
  • callback – an optional callback function which will be called with the component element

Example:

const component = await browser.mountComponent('/src/components/Form.jsx')
const component = await browser.mountComponent('/src/components/Form.jsx', {
  prop: 'value'
})

A function or a string can be used for passing props that cannot be serialized. If a function is passed, it will be sent as a toString() value.

const component = await browser.mountComponent('/src/components/UserInfo.jsx', function () {
  return {
    date: new Date(),
    text: 'I hope you enjoy reading Ulysses!',
    author: {
      name: 'Leopold Bloom',
      avatarUrl: 'https://upload.wikimedia.org/wikipedia/commons/5/52/Poldy.png'
    }
  }
});

- browser.launchComponentRenderer():

This will call browser.navigateTo('/test_renderer/') and open the browser. Needs to be used before the .importScript() command, if used.

You can also set launchUrl as a global at runtime and then the url to be used will be ${browser.globals.launchUrl}/test_renderer, which makes it possible to set the launch url dynamically.

- browser.importScript(scriptPath, [options], [callback]):

Parameters:

  • scriptPath – location of the script file to inject into the page which will render the component; needs to be written in ESM format
  • options – this can include:
    • scriptType: the type attribute to be set on the <script> tag (default is module)
    • componentType: should be set to 'react'
  • callback – an optional callback function which will be called with the component element

Example:

const formComponent = await browser
  .launchComponentRenderer()
  .importScript('/test/lib/scriptToImport.js');

Example scriptToImport.js:

import React from 'react'
import ReactDOM from 'react-dom'
import Component from '/test/components/Form.jsx'

const element = React.createElement(Component, {});
ReactDOM.render(element, document.getElementById('app'));

// This will be used by Nightwatch to inspect properties of this component
window['@@component_element'] = element;

Debugging Component Tests

Debugging component tests in Nightwatch isn't as straightforward as debugging a regular Node.js application or service, since Nightwatch needs to inject the code to render to component into the browser.

However, since Nightwatch v2.4 we provide several ways to inspect and debug the mounted component using the browser devtools console. Refer to the guide page on our docs website for more details: https://nightwatchjs.org/guide/component-testing/debugging.html

Example:

npx nightwatch test/src/userInfoTest.js --devtools --debug

Run tests:

Tests for this project are written in Nightwatch so you can inspect them as examples, located in the [test/src] folder.

Run them with::

npm test 

Example project

We've put together a basic To-do app written in React and built on top of Vite which can be used as a boilerplate. It can be found at nightwatchjs-community/todo-react.

License

MIT