/frameworks/base/tools/aapt2/ |
D | StringPiece_test.cpp | 37 std::u16string testing(u"testing"); in TEST() local 41 EXPECT_TRUE(StringPiece16(testing) > banana); in TEST() 42 EXPECT_TRUE(StringPiece16(testing) > car); in TEST() 43 EXPECT_TRUE(StringPiece16(banana) < testing); in TEST() 45 EXPECT_TRUE(StringPiece16(car) < testing); in TEST() 50 std::string testing("testing"); in TEST() local 54 EXPECT_TRUE(StringPiece(testing) > banana); in TEST() 55 EXPECT_TRUE(StringPiece(testing) > car); in TEST() 56 EXPECT_TRUE(StringPiece(banana) < testing); in TEST() 58 EXPECT_TRUE(StringPiece(car) < testing); in TEST()
|
D | Locale_test.cpp | 25 static ::testing::AssertionResult TestLanguage(const char* input, const char* lang) { in TestLanguage() 30 return ::testing::AssertionFailure() << " failed to parse '" << input << "'."; in TestLanguage() 34 return ::testing::AssertionFailure() << count in TestLanguage() 39 return ::testing::AssertionFailure() << "expected " << lang << " but got " in TestLanguage() 43 return ::testing::AssertionSuccess(); in TestLanguage() 46 static ::testing::AssertionResult TestLanguageRegion(const char* input, const char* lang, in TestLanguageRegion() 52 return ::testing::AssertionFailure() << " failed to parse '" << input << "'."; in TestLanguageRegion() 56 return ::testing::AssertionFailure() << count in TestLanguageRegion() 61 return ::testing::AssertionFailure() << "expected " << input << " but got " in TestLanguageRegion() 66 return ::testing::AssertionFailure() << "expected " << region << " but got " in TestLanguageRegion() [all …]
|
D | XmlFlattener_test.cpp | 36 class XmlFlattenerTest : public ::testing::Test { 52 ::testing::AssertionResult testFlatten(const std::string& in, ResXMLTree* outTree) { in testFlatten() 59 return ::testing::AssertionFailure(); in testFlatten() 65 return ::testing::AssertionFailure(); in testFlatten() 70 return ::testing::AssertionFailure(); in testFlatten() 72 return ::testing::AssertionSuccess(); in testFlatten() 135 ::testing::AssertionResult attributeNameAndValueEquals(ResXMLTree* tree, size_t index, in attributeNameAndValueEquals() 138 return ::testing::AssertionFailure() << "index " << index << " is out of bounds (" in attributeNameAndValueEquals() 143 return ::testing::AssertionFailure() in attributeNameAndValueEquals() 150 return ::testing::AssertionFailure() << "attribute at index " << index << " has value of " in attributeNameAndValueEquals() [all …]
|
D | ConfigDescription_test.cpp | 25 static ::testing::AssertionResult TestParse(const StringPiece& input, in TestParse() 28 return ::testing::AssertionSuccess() << input << " was successfully parsed"; in TestParse() 30 return ::testing::AssertionFailure() << input << " could not be parsed"; in TestParse()
|
/frameworks/base/libs/androidfw/tests/ |
D | TestHelpers.cpp | 25 ::testing::AssertionResult IsStringEqual(const ResTable& table, uint32_t resourceId, const char* ex… in IsStringEqual() 29 return ::testing::AssertionFailure() << "could not find resource"; in IsStringEqual() 33 return ::testing::AssertionFailure() << "resource is not a string"; in IsStringEqual() 38 return ::testing::AssertionFailure() << "table has no string pool for block " << block; in IsStringEqual() 43 return ::testing::AssertionFailure() << actual.string(); in IsStringEqual() 45 return ::testing::AssertionSuccess() << actual.string(); in IsStringEqual()
|
/frameworks/base/docs/html/tools/testing/ |
D | testing-tools.jd | 8 <li><a href="{@docRoot}training/testing.html">Best Practices for Testing</a></li> 23 <dt><strong><a href="{@docRoot}tools/testing-support-library/index.html">Android 31 …<li><a href="{@docRoot}tools/testing-support-library/index.html#AndroidJUnitRunner">AndroidJUnitRu… 35 <li><a href="{@docRoot}tools/testing-support-library/index.html#Espresso">Espresso</a>: 36 UI testing framework; suitable for functional UI testing within an app 39 <li><a href="{@docRoot}tools/testing-support-library/index.html#UIAutomator">UI Automator</a>: 40 …UI testing framework; suitable for cross-app functional UI testing across system and installed apps 53 <dd>This testing system provides an API for writing programs that control an Android device or
|
D | contentprovider_testing.jd | 41 <a href="{@docRoot}tools/testing/activity_test.html">Activity Testing Tutorial</a> 48 href="{@docRoot}tools/testing/testing_android.html"> 52 <a href="{@docRoot}tools/testing/testing_eclipse.html"> 56 <a href="{@docRoot}tools/testing/testing_otheride.html"> 71 familiar with content providers or the Android testing framework, please read 74 <a href="{@docRoot}tools/testing/testing_android.html">Testing Fundamentals</a>, 75 the introduction to the Android testing and instrumentation framework. 95 <a href="{@docRoot}tools/testing/testing_android.html#InstrumentationTestRunner"> 97 more detail. The topic <a href="{@docRoot}tools/testing/testing_eclipse.html"> 99 topic <a href="{@docRoot}tools/testing/testing_otheride.html"> [all …]
|
D | testing_android.jd | 65 <a href="{@docRoot}tools/testing/activity_test.html">Activity Testing Tutorial</a> 71 <a href="{@docRoot}tools/testing/testing_eclipse.html"> 75 <a href="{@docRoot}tools/testing/testing_otheride.html"> 89 The Android testing framework, an integral part of the development environment, 94 The testing framework has these key features: 100 new to Android testing, you can start with general-purpose test case classes such as {@link 121 for testing devices with Python programs, and <a 123 a command-line tool for stress-testing UIs by sending pseudo-random events to a device. 127 This document describes the fundamentals of the Android testing framework, including the 130 programming and JUnit testing methodology. [all …]
|
D | activity_testing.jd | 23 <a href="#MockObjectNotes">Mock objects and activity testing</a> 26 <a href="#AssertionNotes">Assertions for activity testing</a> 63 <a href="{@docRoot}tools/testing/activity_test.html">Activity Testing Tutorial</a> 69 <a href="{@docRoot}tools/testing/testing_eclipse.html"> 73 <a href="{@docRoot}tools/testing/testing_otheride.html"> 80 Activity testing is particularly dependent on the Android instrumentation framework. 88 <a href="{@docRoot}tools/testing/testing_android.html">Testing Fundamentals</a>, 89 the introduction to the Android testing and instrumentation framework. 93 The activity testing API base class is {@link android.test.InstrumentationTestCase}, 97 For activity testing, this base class provides these functions: [all …]
|
D | service_testing.jd | 33 <a href="{@docRoot}tools/testing/activity_test.html">Activity Testing Tutorial</a> 39 <a href="{@docRoot}tools/testing/testing_eclipse.html"> 43 <a href="{@docRoot}tools/testing/testing_otheride.html"> 50 Android provides a testing framework for Service objects that can run them in 56 This document describes techniques for testing Service objects. If you aren't familiar with the 58 Services</a> document. If you aren't familiar with Android testing, please read 59 <a href="{@docRoot}tools/testing/testing_android.html">Testing Fundamentals</a>, 60 the introduction to the Android testing and instrumentation framework. 69 variable for testing purposes. 72 Most other testing is facilitated by the methods in the {@link android.test.ServiceTestCase} [all …]
|
D | index.jd | 4 <p> The Android framework includes an integrated testing framework that helps you test all aspects 9 <p>If you aren't yet familiar with the Android testing framework, start by reading <a 10 href="{@docRoot}tools/testing/testing_android.html">Testing Fundamentals</a>. For a step-by-step 11 introduction to Android testing, try the <a 12 href="{@docRoot}tools/testing/activity_test.html">Activity Testing Tutorial</a>. </p>
|
/frameworks/base/docs/html/training/testing/ui-testing/ |
D | index.jd | 2 page.tags=testing 17 <a href="{@docRoot}tools/testing-support-library/index.html">Testing Support Library</a> 23 <p>User interface (UI) testing lets you ensure that your app meets its functional requirements 27 <p>One approach to UI testing is to simply have a human tester perform a set of user operations on 42 same device as the target app. In your test code, you can use UI testing frameworks to 43 simulate user interactions on the target app, in order to perform testing tasks that cover specific 46 <p>For testing Android apps, you typically create these types of automated UI tests:</p> 52 to user interactions in the app’s activities. UI testing frameworks like Espresso allow you to 57 or with the default Android Photos app. UI testing frameworks that support cross-app interactions, 62 <a href="{@docRoot}tools/testing-support-library/index.html">Android Testing Support Library</a> [all …]
|
/frameworks/base/docs/html/training/activity-testing/ |
D | index.jd | 2 page.tags=testing 20 <li><a href="{@docRoot}tools/testing/index.html">Testing 34 a <em>test runner</em> provided by a testing framework.</p> 37 testing framework that is based on the popular JUnit framework. You can 50 <dt><b><a href="preparing-activity-testing.html">Setting Up Your Test 53 <dt><b><a href="activity-basic-testing.html">Creating and Running a Test 59 <dt><b><a href="activity-ui-testing.html">Testing UI Components</a></b></dt> 62 <dt><b><a href="activity-unit-testing.html">Creating Unit Tests</a></b></dt> 63 <dd>Learn how to how to perform unit testing to 65 <dt><b><a href="activity-functional-testing.html">Creating Functional Tests</a></b></dt> [all …]
|
/frameworks/native/libs/gui/tests/ |
D | GLTest.cpp | 30 const ::testing::TestInfo* const testInfo = in SetUp() 31 ::testing::UnitTest::GetInstance()->current_test_info(); in SetUp() 134 const ::testing::TestInfo* const testInfo = in TearDown() 135 ::testing::UnitTest::GetInstance()->current_test_info(); in TearDown() 175 ::testing::AssertionResult GLTest::checkPixel(int x, int y, in checkPixel() 186 return ::testing::AssertionFailure(::testing::Message(msg.string())); in checkPixel() 210 return ::testing::AssertionFailure(::testing::Message(msg.string())); in checkPixel() 212 return ::testing::AssertionSuccess(); in checkPixel() 216 ::testing::AssertionResult GLTest::assertRectEq(const Rect &r1, const Rect &r2, in assertRectEq() 246 return ::testing::AssertionFailure(::testing::Message(msg.string())); in assertRectEq() [all …]
|
D | GLTest.h | 29 class GLTest : public ::testing::Test { 53 ::testing::AssertionResult checkPixel(int x, int y, 55 ::testing::AssertionResult assertRectEq(const Rect &r1, const Rect &r2,
|
/frameworks/base/tools/aapt/tests/ |
D | AaptGroupEntry_test.cpp | 26 static ::testing::AssertionResult TestParse(AaptGroupEntry& entry, const String8& dirName, in TestParse() 29 return ::testing::AssertionSuccess() << dirName << " was successfully parsed"; in TestParse() 31 return ::testing::AssertionFailure() << dirName << " could not be parsed"; in TestParse() 34 static ::testing::AssertionResult TestParse(AaptGroupEntry& entry, const char* input, in TestParse()
|
D | AaptConfig_test.cpp | 27 static ::testing::AssertionResult TestParse(const String8& input, ConfigDescription* config=NULL) { in TestParse() 29 return ::testing::AssertionSuccess() << input << " was successfully parsed"; in TestParse() 31 return ::testing::AssertionFailure() << input << " could not be parsed"; in TestParse() 34 static ::testing::AssertionResult TestParse(const char* input, ConfigDescription* config=NULL) { in TestParse()
|
/frameworks/base/docs/html/training/testing/unit-testing/ |
D | index.jd | 2 page.tags=testing,androidjunitrunner,junit,unit test 16 <a href="{@docRoot}tools/testing-support-library/index.html">Testing Support Library</a> 22 <p>Unit tests are the fundamental tests in your app testing strategy. By creating and running unit 30 need to verify the logic of specific code in your app. For example, if you are unit testing a 36 <p class="note"><strong>Note:</strong> Unit tests are not suitable for testing 37 complex UI interaction events. Instead, you should use the UI testing frameworks, as described in 38 <a href="{@docRoot}training/testing/ui-testing/index.html">Automating UI Tests</a>.</p> 40 <p>For testing Android apps, you typically create these types of automated unit tests:</p>
|
/frameworks/base/docs/html/training/ |
D | training_toc.cs | 1933 <a href="<?cs var:toroot ?>training/testing.html"> 1940 … <div class="nav-section-header"><a href="<?cs var:toroot ?>training/activity-testing/index.html" 1945 <li><a href="<?cs var:toroot ?>training/activity-testing/preparing-activity-testing.html"> 1949 <li><a href="<?cs var:toroot ?>training/activity-testing/activity-basic-testing.html"> 1953 <li><a href="<?cs var:toroot ?>training/activity-testing/activity-ui-testing.html"> 1957 <li><a href="<?cs var:toroot ?>training/activity-testing/activity-unit-testing.html"> 1961 … <li><a href="<?cs var:toroot ?>training/activity-testing/activity-functional-testing.html"> 1970 … <div class="nav-section-header"><a href="<?cs var:toroot ?>training/testing/ui-testing/index.html" 1975 <li><a href="<?cs var:toroot ?>training/testing/ui-testing/espresso-testing.html"> 1979 <li><a href="<?cs var:toroot ?>training/testing/ui-testing/uiautomator-testing.html"> [all …]
|
/frameworks/base/docs/html-intl/intl/zh-cn/google/play/billing/ |
D | billing_testing.jd | 10 <li><a href="#testing-purchases">测试应用内购买</a></li> 11 <li><a href="#billing-testing-static">使用静态回复进行测试</a></li> 12 <li><a href="#billing-testing-real">设置测试购买</a></li> 31 <h2 id="testing-purchases">测试应用内购买</h2> 54 …试”部分将相应地址添加到<strong>可用于测试的 Gmail 帐户</strong>字段。有关详情,请参阅<a href="#billing-testing-test">设置测试购买</a>。… 90 <h2 id="billing-testing-static">使用静态回复进行测试</h2> 122 …帐户</a>或<a href="{@docRoot}google/play/billing/billing_admin.html#billing-testing-setup">测试帐户</a>时,… 144 <h2 id="billing-testing-test">设置测试真实购买</h2> 150 …试帐户,请参阅<a href="{@docRoot}google/play/billing/billing_admin.html#billing-testing-setup">设置测试帐户</a>… 188 …你可以使用<a href="{@docRoot}google/play/billing/billing_testing.html#billing-testing-static">静态回复</a>和…
|
/frameworks/base/tools/split-select/ |
D | SplitSelector_test.cpp | 29 static ::testing::AssertionResult addSplit(Vector<SplitDescription>& splits, const char* str) { in addSplit() 32 return ::testing::AssertionFailure() << str << " is not a valid configuration."; in addSplit() 35 return ::testing::AssertionSuccess(); in addSplit()
|
D | TestRules.cpp | 74 ::testing::AssertionResult RulePredFormat( in RulePredFormat() 81 return ::testing::AssertionFailure() in RulePredFormat() 85 return ::testing::AssertionSuccess(); in RulePredFormat()
|
/frameworks/base/docs/html-intl/intl/ru/preview/testing/ |
D | performance.jd | 548 …Такие наборы инструментов, как <a href="{@docRoot}training/testing/ui-testing/uiautomator-testing.… 549 <a href="{@docRoot}training/testing/ui-testing/espresso-testing.html">Espresso</a>, 577 …ования интерфейса (такие как <a href="{@docRoot}training/testing/ui-testing/uiautomator-testing.ht…
|
/frameworks/base/tests/utils/SleepUtils/ |
D | README | 14 com.android.testing.sleephelper/.SetAlarm 18 -e param <time in ms> com.android.testing.sleephelper/.SetAlarm 23 com.android.testing.sleephelper/.SetAlarm
|
/frameworks/base/docs/html-intl/intl/zh-tw/preview/testing/ |
D | performance.jd | 548 …oot}training/testing/ui-testing/uiautomator-testing.html">UI Automator</a> 和 <a href="{@docRoot}tr… 577 …直接在目標裝置/模擬器上執行的 UI 測試架構 (例如 <a href="{@docRoot}training/testing/ui-testing/uiautomator-testing.htm…
|