Mercurial > hg > aimc

view wiki/Testing.wiki @ 706:f8e90b5d85fd tip

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Delete CARFAC code from this repository. It has been moved to https://github.com/google/carfac Please email me with your github username to get access. I've also created a new mailing list to discuss CARFAC development: https://groups.google.com/forum/#!forum/carfac-dev
author ronw@google.com
date Thu, 18 Jul 2013 20:56:51 +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.