Hi folks,
i have a question regarding testing infrastructure in the vdr project: Is there any infrastructure for automated tests used by the developer. The only infrastructure i know of is the remote control. svdrp commands could be used for automated testing, but i never seen one using it.
How do you (everyone subscribed to this list) test your developed code ?
Regards, Rainer
On Mon, Aug 2, 2010 at 4:50 AM, Rainer Blickle rainer.blickle@googlemail.com wrote:
i have a question regarding testing infrastructure in the vdr project: Is there any infrastructure for automated tests used by the developer. The only infrastructure i know of is the remote control. svdrp commands could be used for automated testing, but i never seen one using it.
How do you (everyone subscribed to this list) test your developed code ?
I think most people just actually use VDR rather then make some automated method to simulate user activity.
Am 02.08.2010 13:50, schrieb Rainer Blickle:
How do you (everyone subscribed to this list) test your developed code ?
Dogfood testing, mainly. After some manual testing, most stuff quickly moves on to the production system, and if it survives there for some days, its ready to release. After release, any remaining issues usually get reported quickly.
Cheers,
Udo
Rainer Blickle wrote:
How do you (everyone subscribed to this list) test your developed code ?
In the Vodcatcher plugin I used CxxTest:
http://projects.vdr-developer.org/git/?p=vdr-plugin-vodcatcher.git;a=tree
TomG uses CxxTest in the Sudoku plugin as well:
http://projects.vdr-developer.org/git/?p=vdr-plugin-sudoku.git;a=tree
In general unit testing C++ code can be kinda painful compared to Nunit, Junit or RSpec. CxxTest was the best C++ unit testing tool I could find, but maybe there exists something better now.
Besides this you can use Valgrind to hunt down mem leaks and cppcheck for static code analysis.
Tobias
-
Rainer Blickle -
Tobi -
Udo Richter -
VDR User