Editing OctConf 2014
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 115: | Line 115: | ||
== Code Sprint == | == Code Sprint == | ||
The code sprint will be focused on improving | The code sprint will be focused on improving coverage of our test suite. The coverage report is in HTML format and lets you browse through the code tree and see which paths are exercised or not. The latest generated coverage report is [http://hydra.nixos.org/job/gnu/octave-default/coverage/latest/download here]. | ||
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. Keep pulling from Savannah as we keep working on this. | |||
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. | ||
== Participants == | == Participants == | ||
Line 135: | Line 133: | ||
There is limited funding to cover the travel expenses of selected participants. | There is limited funding to cover the travel expenses of selected participants. | ||