Open Source JavaScript Software Testing Tools

Playwright is a Node library for automating Chromium, Firefox and WebKit using a single API. It supports headless execution for all these browsers on Linux, macOS and Windows, providing automated web browser interactions that are fast, capable, reliable and ever-green. Playwright enables a broad spectrum of cross-browser web automation capabilities, which are used by Single Page Apps and Progressive Web Apps. These include scenarios that span multiple pages, domains and iframes; emulation of mobile devices, geolocation, and permissions; upload and download files and many more.

Puppeteer is a headless Node library that provides a high level API for controlling Chromium or Chrome over the DevTools protocol. It requires zero setup and comes bundled with the Chromium version most suited to it. Puppeteer is headless by default, making it fast to run. However, it can also be set to run full or non-headless Chrome or Chromium, simply set the headless option when launching a browser. Many of the things you can do manually in the browser, you can also do with Puppeteer such as generate page screenshots and PDFs, crawl a Single-Page Application, test Chrome extensions and more.

A Javascript framework designed for Web Applicaions.

Playwright for .NET is the official language port of Playwright, the library to automate Chromium, Firefox and WebKit with a single API. Playwright is built to enable cross-browser web automation that is ever-green, capable, reliable and fast. Cross-browser. Playwright supports all modern rendering engines including Chromium, WebKit, and Firefox. Cross-platform. Test on Windows, Linux, and macOS, locally or on CI, headless or headed. Cross-language. Use the Playwright API in TypeScript, JavaScript, Python, .NET, Java. Test Mobile Web. Native mobile emulation of Google Chrome for Android and Mobile Safari. The same rendering engine works on your Desktop and in the Cloud. Auto-wait. Playwright waits for elements to be actionable prior to performing actions. It also has a rich set of introspection events. The combination of the two eliminates the need for artificial timeouts - the primary cause of flaky tests.

A super-agent driven library for testing node.js HTTP servers using a fluent API. The motivation with this module is to provide a high-level abstraction for testing HTTP, while still allowing you to drop down to the lower-level API provided by superagent. Install SuperTest as an npm module and save it to your package.json file as a development dependency. You may pass an http.Server, or a Function to request(), if the server is not already listening for connections then it is bound to an ephemeral port for you so there is no need to keep track of ports. One thing to note, is that superagent now sends any HTTP error (anything other than a 2XX response code) to the callback as the first argument if you do not add a status code expect (i.e. .expect(302)). Expectations are run in the order of definition. This characteristic can be used to modify the response body or headers before executing an assertion.

Gremlins.js is an open-source monkey testing library written in JavaScript. It unleashes a horde of undisciplined gremlins on a web app in order to check its robustness. We've modernized the code of Gremlins.js, our monkey testing library for frontend apps. It's now super easy to detect memory leaks in your JavaScript code. Gremlins.js comes with 5 types of undisciplined gremlins that will try to break your web application: the clicker, the form filler, the scroller, the typer and the toucher. You can also add custom gremlins easily. While gremlins try their best to destroy your app, another type of scripts called mogwais monitor the console errors and the number of frames by second to detect performance problems. Every action performed by the gremlins, and all the errors that might occur, are all logged! In version 2.0, we now use npm to publish the library and unpkg to serve it!

Modern software systems and application are commonly written in multiple languages, include scripting engines, and are frequently build on multiple specialized frameworks and middleware for a considerable diversity of runtime environments. The latest influencing update in development paradigm is the application of multicore processors. This projects is aimed to unify the required trace and logging output and integrate into debugging environments. The target is to provide general development, test, and production support of software environments based on multiple programming languages for distributed multicore environments.