Mercurial > hg > aimc

annotate wiki/Testing.wiki @ 295:9b049b78233d

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Created wiki page through web user interface.
author tomwalters
date Mon, 22 Feb 2010 18:28:02 +0000
parents
children
rev   line source
tomwalters@295 1 #summary Notes on testing AIM-C
tomwalters@295 2 #labels Phase-Design
tomwalters@295 3
tomwalters@295 4 = Unit Tests =
tomwalters@295 5 The goal is for every component of AIM-C to have a corresponding unit test.
tomwalters@295 6 C++ unit testing is done using google test, the testing user interface.
tomwalters@295 7
tomwalters@295 8 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).
tomwalters@295 9
tomwalters@295 10 = Valgrind =
tomwalters@295 11 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.