Use Vogar Expectations to Clean Up Remaining Tests
There were still some core tests that couldn't pass in the overall
CTS run that passed individually. There were also some framework
tests that are also consistently failing.
In the interest of time, these tests will be suppressed. To avoid
a multi-project change, create a expectations file in the CTS
project and use that to filter out some core tests. This approach
actually seems useful, so use to to filter out some of the
framework tests as well! This is probably easier than deleting and
adding annotations!
Change-Id: I93a94c7cf9d388da4fcf0074c6b64688535c25e4
diff --git a/development/ide/eclipse/.classpath b/development/ide/eclipse/.classpath
index 3f11bd1..8cba973 100644
--- a/development/ide/eclipse/.classpath
+++ b/development/ide/eclipse/.classpath
@@ -3,6 +3,7 @@
<classpathentry kind="src" path="cts/apps/CtsVerifier/src"/>
<classpathentry kind="src" path="cts/apps/CtsVerifier/tests/src"/>
<classpathentry kind="src" path="cts/libs/annotation/src"/>
+ <classpathentry kind="src" path="cts/libs/vogar-expect/src"/>
<classpathentry kind="src" path="cts/tests/ApiDemosReferenceTest/src"/>
<classpathentry kind="src" path="cts/tests/ProcessTest/src"/>
<classpathentry kind="src" path="cts/tests/ProcessTest/NoShareUidApp/src"/>