-
Notifications
You must be signed in to change notification settings - Fork 9
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
Convert all doc tests to integration tests #38
Comments
I'm marking this as "good first issue", but I don't expect people to contribute every single integration test in a single PR. If you'd like to add even one good set of testing for a macro i'd accept an improvement in this area. |
Can I use bytemuck for tests? |
yes that's a good idea. |
update: yeah the more i do this the more you can see the speed gains within the test suite. it's boring, but certainly a nice to have. I can continue to convert one module over at a time when i've got an extra boring weekend day or whatever. |
Currently all the tests are done via doc tests.
This means that most functions have only a single test case.
Particularly for a lot of the macros we probably want tests that check all sorts of edge cases. These should be put into the crate as integration tests (that is, modules in the
tests/
folder).The text was updated successfully, but these errors were encountered: