This project is an experiment where I recreate the Node.js test runner using the same components. The primary goal is to understand and demonstrate the functionality of the test runner using:
- Parallelism with Child Processes
- AsyncHooks and Async LocalStorage for tracking the origin and retrieving the entire tree of tests.
- Testing API with hooks such as
describe,it,before,after,beforeEach,afterEach
- app: Contains a complete project which is an API with a comprehensive test suite. This suite tests each individual route and uses the custom test runner to prove the experiment's functionality.
This custom test runner follows all the steps a test runner needs to have:
- Executor: Located at ./test-runner/bin/test-runner.js
- Formatter: Located at ./test-runner/bin/reporter.js
- JS API for Hooks: Located at ./test-runner/module/testRunner.js
AsyncHooks are crucial for this project as they allow tracking the origin and retrieving the entire tree of tests. This helps in understanding which describe block all hooks belong to. Using AsyncHooks, the context of asynchronous operations is maintained, ensuring that hooks like before, after, beforeEach, and afterEach are correctly associated with their respective test cases.
Ensure you have the following installed:
- Node.js (>=20.14)
- Docker and docker-compose (for executing ./app)
git clone https://github.com/ErickWendel/recreating-nodejs-test-runner.gitcd recreating-nodejs-test-runner/app
docker-compose up -d
npm test
Clone the repository and install the dependencies:
cd recreating-nodejs-test-runner/test-runner
npm test
See at the example and execute one of your applications there :)
Contributions are welcome! Please open an issue or submit a pull request for any changes or improvements.
This project is licensed under the MIT License.
- add feature so before and beforeEach executes inside sub suites
- fix log