Groundhog had a user who had reported a lot of bugs which the tests did not capture.
These bugs are mostly located in the SearchGithub class, and are related to some bad url formations.
To handle this problem and avoid future bugs, we must improve the Groundhog unit suit test. We can set the suit test in two levels:
-The first level will be all "sanity" tests that will be runned in every build, they contains the basic of bug repel i.e if this test doesn't pass then something in the new lines of codes is not going in accordance with the system purpose.
-The second level will be a more especific bug radar, will not be at every build and contains all the especific test cases which function is to catch all line of code that break some part of system, make queries that cannot be supported or any change which can be a predict to a bug. To try pass the code, the contributor must chose this option by himself after the first level.
Probably this issue will be open for a long time because we need to build a solid and efficiently test suite to avoid all kinds of bugs and for every new feature in Groundhog means more test. One bug here can be one million in future, so: be humble and just work with small numbers, i.e, improve suit test and avoid bugs.
Groundhog had a user who had reported a lot of bugs which the tests did not capture. These bugs are mostly located in the SearchGithub class, and are related to some bad url formations.
To handle this problem and avoid future bugs, we must improve the Groundhog unit suit test. We can set the suit test in two levels: -The first level will be all "sanity" tests that will be runned in every build, they contains the basic of bug repel i.e if this test doesn't pass then something in the new lines of codes is not going in accordance with the system purpose. -The second level will be a more especific bug radar, will not be at every build and contains all the especific test cases which function is to catch all line of code that break some part of system, make queries that cannot be supported or any change which can be a predict to a bug. To try pass the code, the contributor must chose this option by himself after the first level.
Probably this issue will be open for a long time because we need to build a solid and efficiently test suite to avoid all kinds of bugs and for every new feature in Groundhog means more test. One bug here can be one million in future, so: be humble and just work with small numbers, i.e, improve suit test and avoid bugs.