OpenGrok
Home
Sort by relevance
Sort by last modified time
Full Search
Definition
Symbol
File Path
History
|
|
Help
Searched
full:tests
(Results
176 - 200
of
5234
) sorted by null
1
2
3
4
5
6
7
8
9
10
11
>>
/dalvik/libcore/luni/src/test/java/tests/luni/
AllTestsIo.java
17
package
tests
.luni;
24
* Listing of all the
tests
that are to be run.
34
TestSuite suite =
tests
.TestSuiteFactory.createTestSuite("
Tests
for java.io");
36
suite.addTest(
tests
.api.java.io.AllTests.suite());
38
suite.addTest(org.apache.harmony.luni.
tests
.java.io.AllTests.suite());
AllTestsUtil.java
17
package
tests
.luni;
24
* Listing of all the
tests
that are to be run.
34
TestSuite suite =
tests
.TestSuiteFactory.createTestSuite("
Tests
for java.util");
36
suite.addTest(
tests
.api.java.util.AllTests.suite());
37
suite.addTest(org.apache.harmony.luni.
tests
.java.util.AllTests.suite());
/dalvik/libcore/security/src/test/java/tests/api/java/security/
AllTests.java
17
package
tests
.api.java.security;
23
* This is autogenerated source file. Includes
tests
for package
tests
.api.java.security;
33
TestSuite suite =
tests
.TestSuiteFactory.createTestSuite("All
tests
for package
tests
.api.java.security;");
/dalvik/libcore/security/src/test/java/tests/api/javax/security/cert/
AllTests.java
17
package
tests
.api.javax.security.cert;
23
* This is autogenerated source file. Includes
tests
for package
tests
.api.javax.security.cert;
33
TestSuite suite =
tests
.TestSuiteFactory.createTestSuite("All
tests
for package
tests
.api.javax.security.cert;");
/dalvik/libcore/security/src/test/java/tests/java/security/
AllTests.java
17
package
tests
.java.security;
23
* This is autogenerated source file. Includes
tests
for package
tests
.java.security;
33
TestSuite suite =
tests
.TestSuiteFactory.createTestSuite("All
tests
for package
tests
.java.security;");
/dalvik/libcore/security/src/test/java/tests/security/interfaces/
AllTests.java
17
package
tests
.security.interfaces;
23
* This is autogenerated source file. Includes
tests
for package
tests
.security.interfaces;
33
TestSuite suite =
tests
.TestSuiteFactory.createTestSuite("All
tests
for package
tests
.security.interfaces;");
/dalvik/libcore/sql/src/test/java/org/apache/harmony/sql/tests/javax/sql/
AllTests.java
17
package org.apache.harmony.sql.
tests
.javax.sql;
23
* This is autogenerated source file. Includes
tests
for package org.apache.harmony.sql.
tests
.javax.sql;
33
TestSuite suite =
tests
.TestSuiteFactory.createTestSuite("All
tests
for package org.apache.harmony.sql.
tests
.javax.sql;");
/dalvik/libcore/x-net/src/test/java/tests/api/javax/net/
AllTests.java
17
package
tests
.api.javax.net;
23
* This is autogenerated source file. Includes
tests
for package
tests
.api.javax.net;
33
TestSuite suite =
tests
.TestSuiteFactory.createTestSuite("All
tests
for package
tests
.api.javax.net;");
/external/dbus/test/name-test/
Makefile.am
3
## note that
TESTS
has special meaning (stuff to use in make check)
4
## so if adding
tests
not to be run in make check, don't add them to
5
##
TESTS
8
TESTS
=run-test.sh
10
TESTS
=
17
## we use noinst_PROGRAMS not check_PROGRAMS for
TESTS
so that we
/frameworks/base/keystore/tests/src/android/security/
KeyStoreTestRunner.java
17
package android.security.
tests
;
25
* Instrumentation Test Runner for all KeyStore unit
tests
.
27
* Running all
tests
:
31
* adb shell am instrument -w android.security.
tests
/.KeyStoreTestRunner
39
suite.addTestSuite(android.security.
tests
.KeyStoreTest.class);
40
suite.addTestSuite(android.security.
tests
.SystemKeyStoreTest.class);
/packages/apps/Music/tests/src/com/android/music/
MusicPlayerFunctionalTestRunner.java
17
package com.android.music.
tests
;
21
import com.android.music.
tests
.functional.TestSongs;
22
import com.android.music.
tests
.functional.TestPlaylist;
28
* Instrumentation Test Runner for all Music Player
tests
.
32
* Running all
tests
:
35
* -w com.android.music.
tests
/.MusicPlayerFunctionalTestRunner
MusicPlayerStressTestRunner.java
17
package com.android.music.
tests
;
19
import com.android.music.
tests
.stress.AlbumsPlaybackStress;
20
import com.android.music.
tests
.stress.MusicPlaybackStress;
28
* Instrumentation Test Runner for all music player stress
tests
.
30
* Running all
tests
:
33
* -w com.android.music.
tests
/.MusicPlayerStressTestRunner
/frameworks/base/tests/DumpRenderTree/assets/results/
layout_tests_failed.txt
[
all
...]
/external/gtest/test/
gtest-test-part_test.cc
18
//
Tests
the TestPartResult class.
31
//
Tests
TestPartResult::type().
38
//
Tests
TestPartResult::file_name().
44
//
Tests
TestPartResult::line_number().
50
//
Tests
TestPartResult::message().
55
//
Tests
TestPartResult::passed().
62
//
Tests
TestPartResult::failed().
69
//
Tests
TestPartResult::fatally_failed().
76
//
Tests
TestPartResult::nonfatally_failed().
83
//
Tests
the TestPartResultArray class
[
all
...]
/dalvik/libcore/luni/src/test/java/com/google/coretests/
Main.java
20
import
tests
.AllTests;
23
* Main class to run the core
tests
.
29
System.out.println("Running all
tests
...");
30
CoreTestRunner.main(new String[] { "
tests
.AllTests" });
37
System.out.println("Running all
tests
with stats...");
40
System.out.println("Running selected
tests
with stats...");
44
System.out.println("Running selected
tests
...");
/dalvik/libcore/sql/src/test/java/tests/javax/sql/
ConnectionPoolDataSourceTest.java
1
package
tests
.javax.sql;
19
* @
tests
{@link javax.sql.ConnectionPoolDataSource#getLoginTimeout()}
32
* @
tests
{@link javax.sql.ConnectionPoolDataSource#getLogWriter()}
45
* @
tests
{@link javax.sql.ConnectionPoolDataSource#getPooledConnection()}
58
* @
tests
{@link javax.sql.ConnectionPoolDataSource#getPooledConnection(String, String)}
71
* @
tests
{@link javax.sql.ConnectionPoolDataSource#setLoginTimeout(int)}
84
* @
tests
{@link javax.sql.ConnectionPoolDataSource#setLogWriter(java.io.PrintWriter)}
DataSourceTest.java
1
package
tests
.javax.sql;
18
* @
tests
{@link javax.sql.DataSource#getConnection()}
31
* @
tests
{@link javax.sql.DataSource#getConnection(String, String)}
44
* @
tests
{@link javax.sql.DataSource#getLoginTimeout()}
57
* @
tests
{@link javax.sql.DataSource#getLogWriter()}
70
* @
tests
{@link javax.sql.DataSource#setLoginTimeout(int)}
84
* @
tests
{@link javax.sql.DataSource#setLogWriter(java.io.PrintWriter)}
/dalvik/libcore/xml/src/test/java/tests/xml/
AllTests.java
17
package
tests
.xml;
25
TestSuite suite =
tests
.TestSuiteFactory.createTestSuite();
35
//suite.addTest(
tests
.org.w3c.dom.AllTests.suite());
36
suite.addTest(
tests
.api.javax.xml.parsers.AllTests.suite());
38
suite.addTest(
tests
.api.org.xml.sax.AllTests.suite());
39
suite.addTest(
tests
.api.org.w3c.dom.AllTests.suite());
40
suite.addTest(
tests
.org.w3c.dom.AllTests.suite());
/external/stlport/test/compiler/
README
1
1. About this
tests
3
This is
tests
to check whether compiler understand or not some language
4
construction. It is NOT
tests
for language support libraries, only
tests
for
7
The main purposes of this
tests
is to help for developers to find correct
22
Notes about
tests
.
26
tests
for template-in-the-template explicit specialization.
/packages/apps/Calendar/tests/
AndroidManifest.xml
17
<!-- package name must be unique so suffix with "
tests
" so package loader doesn't ignore us -->
19
package="com.android.calendar.
tests
">
26
The test delcared in this instrumentation will be run along with
tests
declared by
28
The "itr" command will find all
tests
declared by all applications. If you want to run just these
29
tests
on their own then use the command:
30
"adb shell am instrument -w com.android.calendar.
tests
/android.test.InstrumentationTestRunner"
34
android:label="calendar
tests
"/>
/packages/providers/CalendarProvider/tests/
AndroidManifest.xml
17
<!-- package name must be unique so suffix with "
tests
" so package loader doesn't ignore us -->
19
package="com.android.providers.calendar.
tests
">
29
The test declared in this instrumentation will be run along with
tests
declared by
31
The "itr" command will find all
tests
declared by all applications. If you want to run just these
32
tests
on their own then use the command:
33
"adb shell am instrument -w com.android.providers.calendar.
tests
/android.test.InstrumentationTestRunner"
37
android:label="calendar provider
tests
"/>
/dalvik/libcore/luni/src/test/java/tests/api/java/io/
DataInputOutputStreamTest.java
17
package
tests
.api.java.io;
25
import
tests
.support.Support_OutputStream;
43
* @
tests
java.io.DataInputStream#readBoolean()
44
* @
tests
java.io.DataOutputStream#writeBoolean(boolean)
49
notes = "
Tests
against golden file missing.",
55
notes = "
Tests
against golden file missing.",
94
* @
tests
java.io.DataInputStream#readByte()
95
* @
tests
java.io.DataOutputStream#writeByte(int)
100
notes = "
Tests
against golden file missing.",
106
notes = "
Tests
against golden file missing."
[
all
...]
ObjectInputOutputStreamTest.java
17
package
tests
.api.java.io;
25
import
tests
.support.Support_OutputStream;
43
* @
tests
java.io.ObjectInputStream#readBoolean()
44
* @
tests
java.io.ObjectOutputStream#writeBoolean(boolean)
49
notes = "
Tests
against golden file missing. IOException can " +
57
notes = "
Tests
against golden file missing.",
88
* @
tests
java.io.ObjectInputStream#readByte()
89
* @
tests
java.io.ObjectOutputStream#writeByte(int)
94
notes = "
Tests
against golden file missing. IOException can " +
102
notes = "
Tests
against golden file missing."
[
all
...]
/development/pdk/docs/porting/
instrumentation_testing.jd
13
<li><a href="#androidInstrumentationFrameworkWritingRunning">Running
Tests
</a></li>
14
<li><a href="#androidInstrumentationTestingCreating">Writing
Tests
</a></li>
28
<p> Each Android application runs in its own process. Instrumentation kills the application process and restarts the process with Instrumentation. Instrumentation gives a handle to the application context used to poke around the application to validate test assertions, allowing you to write test cases to test applications at a much lower level than UI screen shot
tests
. Note that Instrumentation cannot catch UI bugs. </p>
45
<p>This extends the standard JUnit <code>TestCase</code> and offers access to an <code>Instrumentation</code> class. Write
tests
inside your instrumentation class any way you see fit. For example, your test might launch activities and send key events. For this to work properly, the instrumentation needs to be injected into the test case.</p> </td>
64
<td valign="top"><p>This class can be used to write
tests
for a specific activity. An activity is launched in its <code>setUp()</code> method and finished with <code>tearDown</code>. If you write a test case that extends <code>ActivityTestCase</code>, you can write
tests
that access the activity using <code>getActivity()</code> and assume it has been set up properly.</p></td>
103
<a name="androidTestingPlatformFramework"></a><h4>Framework
Tests
</h4>
105
<p>Framework test cases test the Android application framework or specific Android application functionality that requires an Android runtime context. These
tests
can be found in <code>//device/
tests
</code> and <code>//device/apps/AndroidTests</code>.</p>
110
<p>Core library test cases test the Android library functionality that does not require an Android runtime context. These
tests
are split into Android library (android.* package space) tests at <code>//device/java/tests</code> (…)
[
all
...]
/dalvik/libcore/
AndroidManifest.xml
18
package="android.core.
tests
">
27
android:targetPackage="android.core.
tests
"
28
android:label="cts core
tests
"/>
31
android:targetPackage="android.core.
tests
"
32
android:label="cts core
tests
"/>
Completed in 53 milliseconds
1
2
3
4
5
6
7
8
9
10
11
>>