Mercurial > hg > aimc

view wiki/Testing.wiki @ 557:0fde611fcd10

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
* SUGGESTED re-factor of the FIR_coeffs calls (old code remains in commented out form for easy comparison). * Minor changes to CARFAC and IHC corresponding to MATLAB refactoring
author Ulf.Hammarqvist@gmail.com
date Mon, 09 Apr 2012 09:43:02 +0000
parents 9b049b78233d
children
line wrap: on
line source
#summary Notes on testing AIM-C
#labels Phase-Design

= Unit Tests = 
The goal is for every component of AIM-C to have a corresponding unit test.
C++ unit testing is done using google test, the testing user interface.

Unit tests can also be written in python. Currently these are done on an ad-hoc basis, but they will be replaced eventually with a proper testing framework (hopefully).

= Valgrind =
Valgrind is an excellent tool for detecting memory leaks. When developing modules, it is highly advisable to run valgrind on the aimc executable while it runs a sound file through a complete set of modules.