1 comment

[ 3.6 ms ] story [ 7.3 ms ] thread
Hi. I built a test runner that doesn't have a lot of the features other test runners have.

Why?

Most test runners include a lot of features and do a lot of magic.

They automatically (magically?):

- search and include test files

- run the tests for you

- inject test methods like `describe`/`it`

- add a hooks system for managing `before`/`after` events

- use cli's to manage the auto inclusion of the test runner

- use event systems for capturing when tests fail/succeed/finish

These features can create a great foundation for writing and running tests, but they also come with their own management and overhead.

This library aims to provide a bare bones test runner with zero magic.

As such, it can run in a web browser, nodejs, deno or any other javascript interpreter.

It's also pretty fast, small and has zero dependencies;