android_development

Author	SHA1	Message	Date
Brian Carlstrom	90218acfdf	runtest --path fails with symlinked ANDROID_BUILD_TOP While reproducing b/2558977 I found that "runtest --path" did not work for me because my ANDROID_BUILD_TOP contained a symlink. This is a local fix to make FindTests use os.path.realpath instead of only half using os.path.abspath when trying to make canonical paths to compare. Change-Id: Ief353f52cb80b1798edc3c1233d1e082d9cebc26	2010-04-15 10:36:05 -07:00
Fred Quintana	75a73dc9fb	fix runtest for unqualified Instrumentation class names Change-Id: I0dcc9918b0bde568219d9085e8bbbc4cbba2b552 http://b/issue?id=2472406	2010-03-16 16:27:03 -07:00
Brett Chabot	4a5d9f1ba7	Replace runtest --cts option with more generic --suite option. This will allow you to run a the set of test_defs with attribute suite="foo" like this: runtest --suite foo Bug 2401250	2010-02-19 09:42:17 -08:00
Brett Chabot	59b4778dd6	Add runtest --path. This supports specifying a file system path to test(s) to run. The path can be a java test class file, a java package directory, or a parent directory containing many tests. This change allows users to run tests independently from test_defs.xml. BUG 2133198	2009-10-26 12:22:46 -07:00