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

Consider mutation testing #46

Open
gilch opened this issue Nov 20, 2019 · 2 comments
Open

Consider mutation testing #46

gilch opened this issue Nov 20, 2019 · 2 comments
Labels
automation Tests and workflows and pipelines, oh my

Comments

@gilch
Copy link
Owner

gilch commented Nov 20, 2019

100% test coverage doesn't mean that everything is actually tested. I'm not even sure if I've covered all my lines yet. I think the compiler could use a little refactoring, but I'm not quite confident enough in my tests to try it. I'm not sure which mutation testing package to use yet, or how well Travis or the like can use them.

@gilch
Copy link
Owner Author

gilch commented Oct 5, 2021

I have at least covered all of my lines now. That only means they were run by the tests, not that the tests actually checked everything (but at least they didn't crash). Mutation testing is a much higher level of assurance. I've used mutmut on Python 2 code before, but there may be faster options for Python 3 now.

@gilch
Copy link
Owner Author

gilch commented Oct 5, 2021

I'm also considering full type annotations and CrossHair contracts. That's probably about the best we can do short of rewriting it in Idris and proving theorems.

@gilch gilch added the automation Tests and workflows and pipelines, oh my label May 26, 2023
@gilch gilch mentioned this issue Jun 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation Tests and workflows and pipelines, oh my
Projects
None yet
Development

No branches or pull requests

1 participant