Closed pavpanchekha closed 6 years ago
These latest commits add a unit test for a bug found in Herbgrind, fix bugs in the script so that the test actually fails, pulls the fix, and confirms the test now passes. This is the unit testing workflow in a nutshell!
These latest changes have overhauled the unit test script. It is now simpler and easier to understand: it is a pure textual comparison, except that instruction addresses are masked so that differences do not matter. To make this happen, tests no longer use random numbers; instead, values are hardcoded to hit the problematic cases.
This adds a preliminary Travis build, using the current (checked) output for the existing unit tests. The code is still pretty smelly, but it definitely gets us a working Travis build.