There are dozens of files in our core LIBBN library. As a core library used by nearly every one of BRL-CAD's tools, testing those functions for correct behavior is important.
References:
- include/bn.h
- include/plot3.h
- include/vmath.h
- src/libbn/rand.c
- src/libbu/tests/*.c (note libbu, not libbn for examples)
- src/libbn/tests/*.c (also many examples, but not as good)
Code:
- src/libbn/tests/rand.c
- src/libbn/tests/CMakeLists.txt
This task involves implementing a new unit test for any of LIBBN's source files that do not already have a unit test defined. The test should run at least 10 public functions if there are multiple functions defined within one of our source files.
Some files, like our mat.c file, have LOTS of functions. You don't have to test them all! Just test at least 10 of them and if any prove to be challenging, let us know before you invest more than an hour. Your unit test(s) must be hooked into our build system and "should" pass. If you find a genuine bug, let us know (we can create follow-on tasks for any you investigate and fix). We have lots of existing unit tests to follow as an example.
Submit your new unit test and build system changes as a patch file. Let us know about any problems or bugs encountered.
| File name/URL | File size | Date submitted | |
|---|---|---|---|
| tabdata_tests.diff | 18.3 KB | December 28 2013 17:27 UTC |
I would like to work on this task.
This task has been assigned to Andromeda Galaxy. You have 72 hours to complete this task, good luck!
The work on this task is ready to be reviewed.
Melange has detected that the deadline has passed and no more work can be submitted. The submitted work should be reviewed.
Hi,
I have been traveling and lost a large amount of time on this task due to that; if you are not fully satisfied with the work I submitted, can you please extend the deadline?
Congratulations, this task has been completed successfully.
This looks quite good to me. Remember that now you have commit access, you can commit while you work. You don't have to wait. You can post the commit revision links here instead of needing to upload patch files. That will also give us a sense for how long things are taking so you're credited tasks accordingly.
I can do that if you like; I have not been doing that right now because I thought that it would be a good idea not to commit until I was sure that my work satisfies your expectations, so I like to wait for you to review it...