1,072
edits
OctConf 2014: Difference between revisions
→Code Sprint
| Line 115: | Line 115: | ||
== Code Sprint == | == Code Sprint == | ||
The code sprint will be focused on improving coverage of our test suite. | The code sprint will be focused on improving line coverage of our test suite ('make check'). We're starting the sprint with just 48.1% line coverage. You can see the coverage report in HTML format at [http://hydra.nixos.org/job/gnu/octave-default/coverage/latest/download here]. The report lets you browse through the code tree and see which paths are exercised or not. | ||
To improve things we will be writing tests again. Look through the test coverage, and pick something that doesn't have tests yet. Announce in IRC which function you're going to write a test for. Write it. If you have push access, push your test. Otherwise, post a Mercurial patch that someone else can apply for you. Keep pulling from Savannah as we keep working on this. We are working on the development branch of Mercurial today. | |||
The function 'nchoosek.m' in the scripts/specfun directory is a good small example of built-in self tests using the Octave testing environment. The test platform is documented in Appendix B (Test and Demo Functions) of the Octave manual. Basically, you only need to know regular Octave code to contribute. | The function 'nchoosek.m' in the scripts/specfun directory is a good small example of built-in self tests using the Octave testing environment. The test platform is documented in Appendix B (Test and Demo Functions) of the Octave manual. Basically, you only need to know regular Octave code to contribute. | ||