gtest would be my vote. There are bound to be things we need to test that aren't in the API and this is a good way to do this.
The other thing I can think if is if, for debug builds only, we add a static function that is available in the public API that we can call from our test suite. Then we have a python based test that just does something like: #if defined(LLDB_CONFIGURATION_DEBUG) static void SBDebugger::RunUnitTests(); #endif The in python: debugger.UnitTest() This runs all built in unit test. These tests might need a output format that can be parsed in case any built in unit test fail. Then all classes that want to run unit tests can register a <classname::UnitTest() static function that can be run. http://reviews.llvm.org/D8265 EMAIL PREFERENCES http://reviews.llvm.org/settings/panel/emailpreferences/ _______________________________________________ lldb-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits
