Home
last modified time | relevance | path

Searched refs:assertions (Results 1 – 8 of 8) sorted by relevance

/frameworks/compile/mclinker/include/mcld/
DLinkerScript.h61 const Assertions& assertions() const { return m_Assertions; } in assertions() function
62 Assertions& assertions() { return m_Assertions; } in assertions() function
/frameworks/compile/mclinker/lib/Script/
DAssertCmd.cpp47 pModule.getScript().assertions().push_back(*this); in activate()
/frameworks/compile/mclinker/lib/Object/
DObjectLinker.cpp721 assertEnd = script.assertions().end(); in finalizeSymbolValue()
722 for (assert = script.assertions().begin(); assert != assertEnd; ++assert) { in finalizeSymbolValue()
/frameworks/base/docs/html/training/activity-testing/
Dactivity-unit-testing.jd100 string value to launch the next {@link android.app.Activity}. If both assertions
Dactivity-basic-testing.jd158 class. Generally, you can use assertions to
/frameworks/base/docs/html/tools/testing/
Dtesting_android.jd232 throw an exception if the comparison fails. Android also provides a class of assertions that
233 extend the possible types of comparisons, and another class of assertions for testing the UI.
366 expected value, and throws an AssertionException if the comparison test fails. Using assertions
375 {@link android.test.MoreAsserts} contains more powerful assertions such as
380 {@link android.test.ViewAsserts} contains useful assertions about Views. For example
Dactivity_testing.jd172 {@link android.test.ViewAsserts} defines assertions for Views. You use it to verify the
/frameworks/base/docs/html/guide/topics/providers/
Dcontacts-provider.jd1293 // Adds the assertions to the assert operation: checks the version and count of rows tested