Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch to a testing framework that is not Jest #1102

Open
anton-trunov opened this issue Nov 28, 2024 · 2 comments
Open

Switch to a testing framework that is not Jest #1102

anton-trunov opened this issue Nov 28, 2024 · 2 comments
Assignees
Labels

Comments

@anton-trunov
Copy link
Member

anton-trunov commented Nov 28, 2024

Related to #146

@novusnota
Copy link
Member

novusnota commented Nov 28, 2024

Some options:

  1. "Oxidize" the Jest — no changes to the tests
  2. Vitest — some changes to the tests
  3. Built-in Node.js test runner (since v18) — even more changes to the tests, plus some additional setup of tsx OR using experimental type stripping of Node.js, or its experimental type transformations: node --experimental-transform-types. All to continue writing tests with TypeScript

For all but the first option, one would probably have to rewrite the @ton/test-utils, since they only provide methods for Chai and Jest.

@novusnota
Copy link
Member

novusnota commented Dec 4, 2024

Towards the 3rd point (Node.js built-in runner): https://github.com/bloomberg/ts-blank-space, which comes with an interesting article about it: https://bloomberg.github.io/ts-blank-space/.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants