aiming be to be a faster drop-in replacement to Jest.
This project is still WIP, and I'd be glad to receive issues/PRs to help improve it.
- Drop-in replacement to Jest
- TypeScript and JSX support out of the box
- Supa-fast compilation of test files
- Support of async tests
- Support of both ESM and CJS syntaxes
- Built-in support of benchmark tests
npm install --save-dev geste-testTo run your whole test suite, at the root of your project:
gesteTo run only specific tests:
geste tests/utils/*.ts--update-snapshots: when set, failingexpect.toMatchSnapshot()assertions will update corresponding snapshot files.--bench: run benchmark tests right after unit tests--only-bench: run only benchmark tests and ignore unit tests
Install linkedom and (optionally) @testing-library/jest-dom:
npm install --save-dev linkedom
# optional: for usage with testing-library
npm install --save-dev @testing-library/jest-domCreate a geste.config.ts file at the root of your project (next to package.json):
// geste.config.ts
export default {
setupFiles: ["./setupTests.ts"],
};Then create the setupTests.ts file, which will be ran before each one of your tests (see https://jestjs.io/docs/configuration#setupfiles-array):
// setupTests.ts
import { parseHTML } from "linkedom";
// optional: for usage with testing-library (run `npm install @testing-library/jest-dom`)
import "@testing-library/jest-dom";
const defaultHtml =
'<!doctype html><html><head><meta charset="utf-8"></head><body></body></html>';
const dom = parseHTML(defaultHtml);
const { window } = dom;
const { document } = window;
// add missing window.location property
if (!window.location) {
// @ts-ignore
window.location = { protocol: "http" };
}
// add missing document.getSelection property
if (!document.getSelection) {
// @ts-ignore
document.getSelection = () => ({});
}
// add missing window.getComputedStyled property
if (!window.getComputedStyle) {
// https://github.com/mikemadest/jest-environment-linkedom/blob/main/src/get-computed-style-polyfill.js
function getComputedStyle(element) {
this.el = element;
this.getPropertyValue = function (prop) {
const regExp = /(\-([a-z]){1})/g;
let updatedProp = prop === "float" ? "styleFloat" : prop;
if (regExp.test(updatedProp)) {
updatedProp = updatedProp.replace(regExp, function (match, ...parts) {
return parts[1].toUpperCase();
});
}
return element?.currentStyle?.[updatedProp]
? element.currentStyle[updatedProp]
: null;
};
return this;
}
window.getComputedStyle = getComputedStyle;
}
// add missing default width/height of window (1024x768 is JSDOM's default)
if (!window.innerWidth) {
window.innerWidth = 1024;
}
if (!window.outerWidth) {
window.outerWidth = 1024;
}
if (!window.innerHeight) {
window.innerHeight = 768;
}
if (!window.outerHeight) {
window.outerHeight = 768;
}
// add in global all window's properties that are not already defined
for (const key of Object.getOwnPropertyNames(window).filter(
(k) => !k.startsWith("_") && !global[k]
)) {
global[key] = window[key];
}
global.document = document;
global.window = window;
global.navigator = window.navigator;
window.console = global.console;geste's API aims to be the exact same as Jest's:
describedescribe.eachdescribe.skiptesttest.eachtest.skipitbeforeAllafterAllbeforeEachafterEachjest.fnjest.resetAllMocks
However this is a WIP project so more APIs will be implemented in the future. Feel free to fill in an issue to ask for the APIs you'd like to be implemented in priority.
Check out the examples/ folder to see real usages of geste API.
geste also implements a benchmarking API inspired by Golang's. Benchmark tests are written the same way as unit tests and are launched only when running geste with the --bench option (or --only-bench to run only benchmark tests).
Register a benchmark test.
import { BenchmarkTools } from "geste-test";
benchmark("benchmark factorialize", (b: BenchmarkTools) => {
for (let i = 0; i < b.N; i++) {
factorialize(10);
}
});geste --bench will output something like:
tests/benchmarks.test.ts
b benchmark factorialize 20971520 82ns/op 1714ms
benchmark factorializeis the name of the benchmark test20971520is the number of times your function was able to run in (at least) one second (higher is better)82ns/opindicates how much time each run took in average (lower is better)1714msis the execution time that was needed to run your function20971520times
Skip a benchmark test.
benchmark.each: (cases: any[]) => (desc: string, cb: (b: BenchmarkTools, ...args: any[]) => any) => void
Register a benchmark test for each case provided. Useful to benchmark a function with various inputs.
benchmark.each([[10], [100], [1000]])("benchmark factorialize(%i)", (b, n) => {
for (let i = 0; i < b.N; i++) {
factorialize(n);
}
});This project aims to be a drop-in replacement to Jest, so the configuration options are very much inspired by it.
You can configure geste's options by creating a geste.config.ts file at the root of your project.
These are the default configuration values:
// geste.config.ts
export default {
testPatterns: [
"**/__tests__/**/*.[jt]s?(x)",
"**/?(*.)+(spec|test).[jt]s?(x)",
],
ignorePatterns: ["**/node_modules/**/*"],
setupFiles: [],
throwOnCompilationErrors: true,
};Here are the list of the currently supported configuration options, and their Jest's "equivalent":
testPatterns: array of glob patterns used to walk your project's sources and find test files. Equivalent to Jest'stestMatchignorePatterns: array of glob patterns that will be ignored when looking for test files. Close to Jest'stestPathIgnorePatternsbut here it's a array of glob patterns instead of regexp patterns.setupFiles: array of paths to modules that will be compiled and evaluated before every one of your test files. Equivalent to Jest'ssetupFilesthrowOnCompilationErrors: should geste throw if it encounters an error while compiling a test file. Kinda same as setting Jest'sbailtotrue