jump to navigation

Boomerang testsuite March 11, 2008

Posted by lizardo in Reverse Engineering.
trackback

Last weekend I made my first code contribution to the Boomerang project: I fixed some tests from the testsuite that were segfaulting or failing due to changes in the debug output. After sending the patch to the mailing list, I was given write access to their CVS repository so I can now commit my fixes myself :) .

My plans for now are to:

  1. do test coverage analysis on the current code using gcov/lcov
  2. if coverage is not acceptable, add more tests to the testsuite
  3. when coverage become acceptable (I still need to define the acceptance criterion), I can then starting making improvements or more complex changes to the code

Of course, before doing any big changes that would affect current functionality, I will submit a patch to the list, so other developers can comment on it. That’s the “Open Source way” of development IMHO.