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

[proposal] Only using node testing tools #1779

Open
2 tasks done
jimmywarting opened this issue Aug 24, 2023 · 3 comments
Open
2 tasks done

[proposal] Only using node testing tools #1779

jimmywarting opened this issue Aug 24, 2023 · 3 comments

Comments

@jimmywarting
Copy link
Contributor

Describe the feature

I would like (if you agree) to refactor the spec/test to only using node:assert and possible get rid of any outdated dependency.

Checklist

  • I have searched through GitHub issues for similar issues.
  • I have completely read through the README and documentation.
@jimmywarting
Copy link
Contributor Author

I have not been such a huge fan of things such as res.text.should.equal('{"name":"hal 5000"}');

should pollutes global built in prototypes chain with things you believe are part of the package when it is in fact not.

@titanism
Copy link
Collaborator

Definitely down to use built-in Node test stuff, either that or Ava like we did with https://github.com/breejs/bree

@jimmywarting
Copy link
Contributor Author

I prefer dependency free stuff.
now that NodeJS have also a built in test runner also node:test and also a node:assert, then i have stop installing any additional dependencies.

the latest version of node testing tools have really grown to be something 👌

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

No branches or pull requests

2 participants