Orchestrate package testing across uneven terrain
Today, people can consume your package in many contexts—in Node.js, in a browser, in an ECMAScript module, in a Common JS module, within a library (e.g., React, Angular, etc.), with assistance from compilers/transpilers/bundlers (e.g., TypeScript, Babel, Webpack, etc.), even inside test runners (e.g., Jest, Mocha, etc.). Each of these contexts has a unique set of capabilities, limitations, requirements, global variables, etc. that could impact or even break your package’s behavior.
Further, testing often only occurs against the source files that are available in the repository, which is problematic in two ways… First, tools may manipulate the source code in such a way that the compiled/transpiled/bundled version behaves slightly differently than the source code. Second, misconfigurations in your
package.json may cause necessary files to be excluded from the published version of your package.
How Rugged helps
Rugged facilitates testing your package in the environments and contexts where your package will be used, using the files that would be published (i.e., the compiled/transpiled/bundled files that are included according to your
This is done by injecting the compiled & packaged version of your package into a series of minimal test projects you create, which mimic the various contexts in which your package could be used/consumed. These test projects live in your package’s repository and simply need a
test script in their
package.json files. Rugged will run the
test script in each test project to verify your package works as expected in each environment/context.
Rugged is designed to be fast and efficient out-of-the-box, with a small size and few dependencies.
Use Rugged both from a terminal during local development and in continuous integration environments.
An extensive suite of automated tests verifies every change to the codebase.
Carefully crafted to produce visually appealing output for both successes and failure.