To celebrate 50,000 thoughts, 50,000 number crunches, and 50,000 sets of passing tests (ok, almost 50,000 sets of passing tests ), let’s hold an online hackathon.
What: A hackathon to celebrate 50,000 commits to the ITK source code repository. Who: Members of the global ITK community, from past, present, to future. Where: Join the event with this video conferencing link:
Congratulations! A Celebration Hackathon, that’s great, @matt.mccormick!
I hope there can be special attention at the Hackaton towards adding and improving unit tests. Now that ITK uses GoogleTest, writing unit tests is much more fun than it was before.
@Niels_Dekker brilliant idea – more GoogleTests are achievable for newcomers during the hackathon, and it is a good opportunity to improve our code coverage.
Perhaps we can reference a few excellent GoogleTest examples to serve as a guide in the Google Doc? List classes in need of improved coverage with GoogleTest?
Rather than writing some “random” tests for “forgotten classes”, it could be (more) interesting to focus on tests for new ITK5 features, and for recent (ITK5) code changes. But of course, it could still be useful to add more tests for frequently used classes that are still from <= ITK4.
I do especially like small test functions that each check one specific requirement of a class (instead of having a single test function checking many different aspects of a class). This is especially well supported by GTest, in my opinion.
If you start creating issues now, you can steer the focus towards that! And the more issues you propose, the less issues the rest of us will have to propose
), let’s hold an online hackathon.
