Any thoughts on the structure underneath gtest?
One idea is, for the case of unittests, where the goal is to directly test
class functionality:
gtest/unittest/{MIRROR_lldb_source_path_to_class_dir}
e.g. for the new source/Plugins/Process/Linux/ThreadStateCoordinator.cpp:
BTW I'll have that fixed up and checked in soon, I'm just fixing a couple
issues with build directory changes and getting it hooked into Xcode.
On Thu, Sep 25, 2014 at 10:43 AM, Todd Fiala tfi...@google.com wrote:
Yeah, took me a minute to sort that out since the Python package that
the
Yeah, took me a minute to sort that out since the Python package that the
regular testsuite uses is called unittest...
A, ok. Yeah I didn't even consider that. I'm not too worried about
confusion there. I'm expecting this will be a relatively low-traffic
directory, and it's scoped to
Fixed this up here:
svn commit
Adding gtest
Adding gtest/Makefile
Adding gtest/gtest.xcodeproj
Adding gtest/gtest.xcodeproj/project.pbxproj
Adding gtest/make
Adding gtest/make/Makefile.rules
Adding gtest/unittest
Adding
Author: tfiala
Date: Wed Sep 24 17:57:33 2014
New Revision: 218422
URL: http://llvm.org/viewvc/llvm-project?rev=218422view=rev
Log:
The beginnings of a gtest-based test framework.
Makes use of LLVM gtest support. This does *not* run as part of
the lldb test suite.
I'm using it to start testing
