Johnny Chen b7373c92e6 o lldbtest.py: ... Assign the test method name to self.testMethodName. This can be useful for the test directory (see test/types for a good example) which houses a bunch of executables compiled from different source files. The default build action is to create a.out as the binary executable, which can confuse the module cacheing mechanism and result in the debugger getting a stale image as the target to be debugged, and chaos ensues. o AbstractBase.py, TestThreadAPI.py: Use self.testMethodName to our advantage. o TestLoadUnload.py: Add expected failure marker to test case test_modules_search_paths(). llvm-svn: 133768		2011-06-23 22:11:20 +00:00
..
AbstractBase.py	o lldbtest.py:	2011-06-23 22:11:20 +00:00
HideTestFailures.py	Modify the test cases (there are a bunch of them) under test/types so that they	2011-06-22 21:15:10 +00:00
Makefile	…
TestFloatTypes.py	Refactorings of the test/types directory to more elegantly express the uniqueness of	2011-06-23 20:10:23 +00:00
TestFloatTypesExpr.py	Refactorings of the test/types directory to more elegantly express the uniqueness of	2011-06-23 20:10:23 +00:00
TestIntegerTypes.py	Refactorings of the test/types directory to more elegantly express the uniqueness of	2011-06-23 20:10:23 +00:00
TestIntegerTypesExpr.py	Refactorings of the test/types directory to more elegantly express the uniqueness of	2011-06-23 20:10:23 +00:00
basic_type.cpp	Simplify the the generic AbstractBase.py test base for testing variable types.	2011-06-21 00:13:15 +00:00
char.cpp	…
double.cpp	…
float.cpp	…
int.cpp	…
long.cpp	…
long_long.cpp	…
short.cpp	…
unsigned_char.cpp	…
unsigned_int.cpp	…
unsigned_long.cpp	…
unsigned_long_long.cpp	…
unsigned_short.cpp	…