Valgrind is an extremely useful tool for finding and catching bugs related to memory management such as branching off of unitialized values, other uses of uninitialized values (reads and writes), memory leaks, and bad array accesses.
By regularly testing your code with valgrind, you can ensure that any changes that might have introduced an issue are quickly identified and fixed.
This is a relatively simple task, so we give it 5pts of extra-credit.
Tasks
[ ] Determine how to modify github actions or other automated testing frameworks to create an additional "action"
[ ] Define the action to run valgrind.
[ ] Have the test results posted somewhere that is accessible for project members
Definition of Done
Evidence of the library tests being run under valgrind is posted somewhere under this github repo.
Background
Valgrind is an extremely useful tool for finding and catching bugs related to memory management such as branching off of unitialized values, other uses of uninitialized values (reads and writes), memory leaks, and bad array accesses.
By regularly testing your code with valgrind, you can ensure that any changes that might have introduced an issue are quickly identified and fixed.
This is a relatively simple task, so we give it 5pts of extra-credit.
Tasks
Definition of Done
Evidence of the library tests being run under valgrind is posted somewhere under this github repo.