Opened 12 years ago
Closed 12 years ago
#3 closed enhancement (invalid)
[Discussion] Code coverage
| Reported by: | melon | Owned by: | melon |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | core | Version: | 0.1 |
| Keywords: | test | Cc: | epyon |
Description
It has be decided which till will we use to test the code coverage. For Linux this could be gcov/lcov.
By adding such feature, we will know exactly what was tested and what needs to be tested. This will reduce for some bugs to be left unspotted.
Change History (3)
comment:1 Changed 12 years ago by epyon
comment:2 Changed 12 years ago by epyon
Higher priority would be doxymenting more of the code. However I have second thoughts in terms of doxymenting an interface (device.hh) in terms of how to doxyment a implementation (gl_device.hh). Any ideas?
comment:3 Changed 12 years ago by epyon
- Resolution set to invalid
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
I don't know if we really want to go there. Especially with the heavy templated stuff -- it would require a *lot* of test code. OTOH, a lot of the things require a visible GL context, and I don't know how LCOV handles that. We could see how much functionality do our tests cover, though.