-
Notifications
You must be signed in to change notification settings - Fork 240
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
Add testing into Chainsaw #50
Conversation
This also contains some refactoring that was required to open up chainsaw so that we can start testing properly. As a result we have a little bit of pub leaking going on here. But this will be addressed affter the rest of the tests are written.
Code tests for hunt/search are too hard to plug in without rework. For now we will tests these with scripts on the complete binary, so that we can ensure that nothing is broken when the refactor is started. |
These are not permanent tests, the script is very very basic. Its sole purpose is to allow for a chainsaw refactor. These diffs will allow for extensive changes to be made with assurance that the output is still correct. Once the refactor is done there should be sufficient native testing that this e2e suite will not need expansion.
Have added a crude script that will diff the output of chainsaw. This will enable the refactor as we can be certain that we are not regressing the code. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've updated the hunt_expected json file to be the latest version. This all looks good now.
In order for us to grow Chainsaw and look after it we need to add tests which were skipped on release due to timing constraints. I have added the most important ones first.
Once all of the above is done, then the big refactor in prep for 2.0 can begin.