Mercurial > hg > aimc
view wiki/Testing.wiki @ 400:dd13c9834ceb
- Well, most of the graphics stuff at least compiles now. Next step is getting it running.
M Modules/Output/Graphics/GraphicsView.h
M Modules/Output/Graphics/Devices/GraphicsOutputDeviceMovieDirect.cc
M Modules/Output/Graphics/Devices/GraphicsOutputDeviceMovieDirect.h
M Modules/Output/Graphics/Devices/GraphicsOutputDeviceCairo.cc
M Modules/Output/Graphics/Devices/GraphicsOutputDeviceCairo.h
M Modules/Output/Graphics/Devices/GraphicsOutputDeviceMovie.cc
M Modules/Output/Graphics/Devices/GraphicsOutputDeviceMovie.h
M Modules/Output/Graphics/Scale/ScaleLog.h
M Modules/Output/Graphics/Scale/ScaleERB.h
M Modules/Output/Graphics/Scale/ScaleLinear.h
M Modules/Output/Graphics/Scale/ScaleLogScaled.h
M Modules/Output/Graphics/Scale/Scale.cc
M Modules/Output/Graphics/Scale/Scale.h
M Support/Common.h
author | tom@acousticscale.org |
---|---|
date | Sat, 16 Oct 2010 23:05:26 +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.