finds.dev← search

// the find

nightwatchjs/nightwatch

★ 11,951 · JavaScript · MIT · updated May 2026

Integrated end-to-end testing framework written in Node.js and using W3C Webdriver API. Developed at @browserstack

Nightwatch is a Node.js end-to-end testing framework that drives browsers through the W3C WebDriver protocol, so the same test code can run against any compliant driver. It suits teams that want one runner for E2E, component, API, accessibility and visual regression tests, and that are comfortable with a Selenium-style command API.

Because it speaks standard WebDriver rather than a proprietary browser channel, the same tests can target chromedriver, geckodriver, safaridriver, or an Appium server for native mobile, and you are not locked to one browser vendor's tooling. Component testing for React, Vue, Angular and Storybook has its own guide and is a real feature, not a demo, which means you can test components without adding a second tool. The project is still getting commits (last push late May 2026), and the npm init nightwatch@latest scaffold generates a working config and example tests on first run.

The pitch covers E2E, component, unit, visual regression, accessibility, API testing and Appium mobile in one package, so each of those areas is judged against single-purpose tools. The visual regression and axe-core pieces are plugins, and the README says nothing about how deep they go. As a WebDriver tool it carries the Selenium-era burden of explicit waits and driver binaries that must match browser versions. The v3 claim of 'consistent non-flaky results' is not backed by anything in the README about how waiting or retries work, and several examples point at BrowserStack's cloud grid, so the local-only experience gets less attention.

View on GitHub → Homepage ↗

// want more like this?

We dig through GitHub every week and send a few repos picked for what you actually care about — each with an honest take like this one.

Get finds in your inbox → Search again →