/bionic/tests/ |
strings_test.cpp | 22 TEST(strings, ffs) {
|
/dalvik/unit-tests/ |
dvmHumanReadableDescriptor_test.cpp | 5 TEST(dvmHumanReadableDescriptor, ArrayReferences) { 10 TEST(dvmHumanReadableDescriptor, ScalarReferences) { 15 TEST(dvmHumanReadableDescriptor, PrimitiveArrays) { 34 TEST(dvmHumanReadableDescriptor, PrimitiveScalars) {
|
/external/chromium/chrome/browser/autofill/ |
autofill_country_unittest.cc | 12 // Test the constructor and accessors 13 TEST(AutofillCountryTest, AutofillCountry) { 35 // Test locale to country code mapping. 36 TEST(AutofillCountryTest, CountryCodeForLocale) { 46 // Test mapping of localized country names to country codes. 47 TEST(AutofillCountryTest, GetCountryCode) {
|
autofill_type_unittest.cc | 10 TEST(AutofillTypeTest, Basic) {
|
/external/chromium/chrome/browser/content_settings/ |
content_settings_pattern_unittest.cc | 12 TEST(ContentSettingsPatternTest, PatternSupport) { 17 EXPECT_TRUE(ContentSettingsPattern("file:///tmp/test.html").IsValid()); 28 EXPECT_TRUE(ContentSettingsPattern("file:///tmp/test.html").Matches( 29 GURL("file:///tmp/test.html"))); 36 EXPECT_FALSE(ContentSettingsPattern("file:///tmp/test.html").Matches( 38 EXPECT_FALSE(ContentSettingsPattern("file:///tmp/test.html").Matches( 42 TEST(ContentSettingsPatternTest, CanonicalizePattern) { 64 EXPECT_STREQ("file:///tmp/test.html", ContentSettingsPattern( 65 "file:///tmp/bar/../test.html").CanonicalizePattern().c_str());
|
/external/chromium/chrome/common/ |
content_settings_helper_unittest.cc | 11 TEST(ContentSettingsHelperTest, OriginToString16) {
|
/external/chromium/testing/gmock/test/ |
gmock-port_test.cc | 40 // test here to make references to symbols in the gtest library and avoid 43 TEST(DummyTest, Dummy) {}
|
/external/chromium/testing/gtest/samples/ |
sample1_unittest.cc | 35 // This sample shows how to write a simple unit test for a function, 38 // Writing a unit test using Google C++ testing framework is easy as 1-2-3: 42 // test logic needs is declared. 51 // Step 2. Use the TEST macro to define your tests. 53 // TEST has two parameters: the test case name and the test name. 54 // After using the macro, you should define your test logic between a 56 // success or failure of a test. EXPECT_TRUE and EXPECT_EQ are 61 // In Google Test, tests are grouped into test cases. This is how w [all...] |
/external/chromium/testing/gtest/test/ |
gtest_help_test_.cc | 38 // and exit with 0; otherwise the following test will be executed, 40 TEST(HelpFlagTest, ShouldNotBeRun) { 45 TEST(DeathTest, UsedByPythonScriptToDetectSupportForDeathTestsInThisBinary) {}
|
gtest_main_unittest.cc | 39 TEST(GTestMainTest, ShouldSucceed) {
|
/external/clang/unittests/Basic/ |
CharInfoTest.cpp | 17 TEST(CharInfoTest, validateInfoTable) { 43 TEST(CharInfoTest, isASCII) { 54 TEST(CharInfoTest, isIdentifierHead) { 74 TEST(CharInfoTest, isIdentifierBody) { 94 TEST(CharInfoTest, isHorizontalWhitespace) { 116 TEST(CharInfoTest, isVerticalWhitespace) { 138 TEST(CharInfoTest, isWhitespace) { 160 TEST(CharInfoTest, isDigit) { 181 TEST(CharInfoTest, isHexDigit) { 202 TEST(CharInfoTest, isLetter) [all...] |
/external/gtest/samples/ |
sample1_unittest.cc | 35 // This sample shows how to write a simple unit test for a function, 38 // Writing a unit test using Google C++ testing framework is easy as 1-2-3: 42 // test logic needs is declared. 51 // Step 2. Use the TEST macro to define your tests. 53 // TEST has two parameters: the test case name and the test name. 54 // After using the macro, you should define your test logic between a 56 // success or failure of a test. EXPECT_TRUE and EXPECT_EQ are 61 // In Google Test, tests are grouped into test cases. This is how w [all...] |
/external/gtest/test/ |
gtest_help_test_.cc | 38 // and exit with 0; otherwise the following test will be executed, 40 TEST(HelpFlagTest, ShouldNotBeRun) { 45 TEST(DeathTest, UsedByPythonScriptToDetectSupportForDeathTestsInThisBinary) {}
|
gtest_main_unittest.cc | 39 TEST(GTestMainTest, ShouldSucceed) {
|
/external/libvpx/libvpx/third_party/googletest/src/samples/ |
sample1_unittest.cc | 35 // This sample shows how to write a simple unit test for a function, 38 // Writing a unit test using Google C++ testing framework is easy as 1-2-3: 42 // test logic needs is declared. 51 // Step 2. Use the TEST macro to define your tests. 53 // TEST has two parameters: the test case name and the test name. 54 // After using the macro, you should define your test logic between a 56 // success or failure of a test. EXPECT_TRUE and EXPECT_EQ are 61 // In Google Test, tests are grouped into test cases. This is how w [all...] |
/external/libvpx/libvpx/third_party/googletest/src/test/ |
gtest_help_test_.cc | 38 // and exit with 0; otherwise the following test will be executed, 40 TEST(HelpFlagTest, ShouldNotBeRun) { 45 TEST(DeathTest, UsedByPythonScriptToDetectSupportForDeathTestsInThisBinary) {}
|
gtest_main_unittest.cc | 39 TEST(GTestMainTest, ShouldSucceed) {
|
/external/llvm/unittests/ADT/ |
IntEqClassesTest.cpp | 17 TEST(IntEqClasses, Simple) {
|
/external/llvm/unittests/Support/ |
LeakDetectorTest.cpp | 19 TEST(LeakDetector, Death1) {
|
ProcessTest.cpp | 22 TEST(ProcessTest, SelfProcess) {
|
/external/markdown/MarkdownTest/ |
MarkdownTest.pl | 44 TEST: 55 next TEST; 58 # open(TEST, $testfile) || die("Can't open testfile: $!"); 61 # my $t_input = <TEST>; 122 Specify the path to the Markdown script to test. Defaults to 129 Specify the path to a directory containing test data. Defaults to "Tests". 134 output before comparing script output to the expected test result.
|
/external/protobuf/gtest/samples/ |
sample1_unittest.cc | 35 // This sample shows how to write a simple unit test for a function, 38 // Writing a unit test using Google C++ testing framework is easy as 1-2-3: 42 // test logic needs is declared. 51 // Step 2. Use the TEST macro to define your tests. 53 // TEST has two parameters: the test case name and the test name. 54 // After using the macro, you should define your test logic between a 56 // success or failure of a test. EXPECT_TRUE and EXPECT_EQ are 61 // In Google Test, tests are grouped into test cases. This is how w [all...] |
/external/protobuf/gtest/test/ |
gtest_help_test_.cc | 38 // and exit with 0; otherwise the following test will be executed, 40 TEST(HelpFlagTest, ShouldNotBeRun) {
|
gtest_main_unittest.cc | 39 TEST(GTestMainTest, ShouldSucceed) {
|
/external/webkit/Source/WebKit/chromium/tests/ |
TilingDataTest.cpp | 41 TEST(TilingDataTest, numTiles_NoTiling) 50 TEST(TilingDataTest, numTiles_TilingNoBorders) 101 TEST(TilingDataTest, numTiles_TilingWithBorders) 153 TEST(TilingDataTest, tileXIndexFromSrcCoord) 181 TEST(TilingDataTest, tileYIndexFromSrcCoord) 210 TEST(TilingDataTest, tileSizeX) 234 TEST(TilingDataTest, tileSizeY) 259 TEST(TilingDataTest, tileSizeX_and_tilePositionX) 314 TEST(TilingDataTest, tileSizeY_and_tilePositionY) 369 TEST(TilingDataTest, setTotalSize [all...] |