poku

Poku

Enjoying Poku? Give him a star to show your support 🌟

---

🐷 Website  •  📒 Documentation  •  🧪 Examples  •  🧑🏻‍🎓 Quick Tutorials

---

Why does Poku exist?

💡 Poku makes testing easy and brings the native JavaScript syntax back to tests, letting you to write tests intuitively — just like in real JavaScript code.

No configurations
      Auto detect ESM, CJS, and TypeScript files
      Run the same test suite for Node.js, Bun, and Deno

Easier and Less Verbose
      Node.js familiar API
      Instantly re-run related tests in watch mode
      Run CJS (CommonJS) files directly with Deno
      Easily handle containers, servers, services, processes, and ports

Safety and Reliability
      High isolation level per file
      Performant and lightweight
      Compatible with coverage tools

---

Quickstart

Install

Node.js	TypeScript + Node.js	Bun	Deno
npm i -D poku	npm i -D poku tsx	bun add -d poku	deno add npm:poku

Test

test/file.test.mjs

import { assert } from 'poku'; assert(true, 'Poku will describe it 🐷');

Run

Node.js (and TypeScript)	Bun	Deno
npx poku	bunx poku	deno run npm:poku

Try the flag --parallel to run tests in parallel.

• That's it 🎉

---

Available Methods

Essentials

• poku (test runner)
• assert (test assertion)

Helpers

• test, describe and it (organize, group, and isolate tests)
• beforeEach and afterEach (hooks for test setup and teardown)
• docker (build, start, compose, stop, remove, and test containers)
• startScript (run package.json scripts in background)
• startService (run files in background)
• kill (terminate ports, port ranges, and PIDs)
• waitForPort (wait for specified ports to become active)
• waitForExpectedResult (retry until an expected result or times out)
• getPIDs (debug processes IDs using ports and port ranges)

Common Options

• watch (watch for changes and re-run related test files)
• parallel (run tests in parallel)
• debug (shows all logs)

and much more 👇🏻

---

Documentation and Examples

To see the detailed documentation, please visit the Documentation and Examples sections in the Poku's website.

---

Tutorials

Poku offers mini-lessons for different users needs in the Quick Tutorials section.

---

Common Issues

• Avoiding conflicts in environments with multiple platforms installed.
• Properly running asynchronous tests on the same file.

---

Contributing

See the Contributing Guide and please follow our Code of Conduct 🚀

---

Security Policy

Please check the SECURITY.md.

---

Quick Comparisons

Performance

Poku is continuously tested to ensure the following expectations for basic usage:

• ~4x faster than Jest (v29.7.0)
• ~3x faster than Vitest (v1.6.0)
• ~1x faster than Mocha (v10.4.0) + Chai (v5.1.1)

You can see how the tests are run and compared in the benchmark directory.

---

Installation Size

• ~300x lighter than Vitest
• ~170x lighter than Jest
• ~40x lighter than Mocha + Chai

Poku size is highly significant in development to ensure cost-saving CI that require servers that charge for storage and usage.

---

Limitations

• Although it has no external dependencies, Poku is not all-in-one, so it doesn't have integrated features such as mocks, spies, coverage reports, etc., where you can use your favorite packages or native solutions.
  • See a mock example.
• Poku doesn't render components (such as Angular, React, etc.).
  • See an end-to-end test example.
• Our community is gradually building up.

---

Acknowledgements

---

License

Poku is under the MIT License.