diff options
Diffstat (limited to 'testapps/libsTest/lib2Test')
-rw-r--r-- | testapps/libsTest/lib2Test/.classpath | 8 | ||||
-rw-r--r-- | testapps/libsTest/lib2Test/.project | 34 | ||||
-rw-r--r-- | testapps/libsTest/lib2Test/AndroidManifest.xml | 30 | ||||
-rw-r--r-- | testapps/libsTest/lib2Test/build.xml | 92 | ||||
-rw-r--r-- | testapps/libsTest/lib2Test/proguard-project.txt | 20 | ||||
-rw-r--r-- | testapps/libsTest/lib2Test/project.properties | 16 | ||||
-rw-r--r-- | testapps/libsTest/lib2Test/res/values/strings.xml | 6 | ||||
-rw-r--r-- | testapps/libsTest/lib2Test/src/com/android/tests/libstest/lib2/MainActivityTest.java | 86 |
8 files changed, 0 insertions, 292 deletions
diff --git a/testapps/libsTest/lib2Test/.classpath b/testapps/libsTest/lib2Test/.classpath deleted file mode 100644 index a4763d1ee..000000000 --- a/testapps/libsTest/lib2Test/.classpath +++ /dev/null @@ -1,8 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<classpath> - <classpathentry kind="src" path="src"/> - <classpathentry kind="src" path="gen"/> - <classpathentry kind="con" path="com.android.ide.eclipse.adt.ANDROID_FRAMEWORK"/> - <classpathentry kind="con" path="com.android.ide.eclipse.adt.LIBRARIES"/> - <classpathentry kind="output" path="bin/classes"/> -</classpath> diff --git a/testapps/libsTest/lib2Test/.project b/testapps/libsTest/lib2Test/.project deleted file mode 100644 index 5ef5c2c47..000000000 --- a/testapps/libsTest/lib2Test/.project +++ /dev/null @@ -1,34 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<projectDescription> - <name>libsTest-lib2Test</name> - <comment></comment> - <projects> - <project>testProjectTest-app</project> - </projects> - <buildSpec> - <buildCommand> - <name>com.android.ide.eclipse.adt.ResourceManagerBuilder</name> - <arguments> - </arguments> - </buildCommand> - <buildCommand> - <name>com.android.ide.eclipse.adt.PreCompilerBuilder</name> - <arguments> - </arguments> - </buildCommand> - <buildCommand> - <name>org.eclipse.jdt.core.javabuilder</name> - <arguments> - </arguments> - </buildCommand> - <buildCommand> - <name>com.android.ide.eclipse.adt.ApkBuilder</name> - <arguments> - </arguments> - </buildCommand> - </buildSpec> - <natures> - <nature>com.android.ide.eclipse.adt.AndroidNature</nature> - <nature>org.eclipse.jdt.core.javanature</nature> - </natures> -</projectDescription> diff --git a/testapps/libsTest/lib2Test/AndroidManifest.xml b/testapps/libsTest/lib2Test/AndroidManifest.xml deleted file mode 100644 index e6b59a1fb..000000000 --- a/testapps/libsTest/lib2Test/AndroidManifest.xml +++ /dev/null @@ -1,30 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<manifest xmlns:android="http://schemas.android.com/apk/res/android" - xmlns:tools="http://schemas.android.com/tools" - package="com.android.tests.libstest.lib2.test" - android:versionCode="1" - android:versionName="1.0" > - - <uses-sdk - android:minSdkVersion="15" - tools:ignore="UsesMinSdkAttributes" /> - - <!-- - We add an application tag here just so that we can indicate that - this package needs to link against the android.test library, - which is needed when building test cases. - --> - <application android:label="testProjectTest-testlib" > - <uses-library android:name="android.test.runner" /> - </application> - - <!-- - This declares that this app uses the instrumentation test runner targeting - the package of com.android.tests.testprojecttest.testlib. To run the tests use the command: - "adb shell am instrument -w com.android.tests.testprojecttest.testlib/android.test.InstrumentationTestRunner" - --> - <instrumentation - android:name="android.test.InstrumentationTestRunner" - android:targetPackage="com.android.tests.libstest.lib2.test" /> - -</manifest>
\ No newline at end of file diff --git a/testapps/libsTest/lib2Test/build.xml b/testapps/libsTest/lib2Test/build.xml deleted file mode 100644 index b59cc6570..000000000 --- a/testapps/libsTest/lib2Test/build.xml +++ /dev/null @@ -1,92 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<project name="testProjectTest-testlib" default="help"> - - <!-- The local.properties file is created and updated by the 'android' tool. - It contains the path to the SDK. It should *NOT* be checked into - Version Control Systems. --> - <property file="local.properties" /> - - <!-- The ant.properties file can be created by you. It is only edited by the - 'android' tool to add properties to it. - This is the place to change some Ant specific build properties. - Here are some properties you may want to change/update: - - source.dir - The name of the source directory. Default is 'src'. - out.dir - The name of the output directory. Default is 'bin'. - - For other overridable properties, look at the beginning of the rules - files in the SDK, at tools/ant/build.xml - - Properties related to the SDK location or the project target should - be updated using the 'android' tool with the 'update' action. - - This file is an integral part of the build system for your - application and should be checked into Version Control Systems. - - --> - <property file="ant.properties" /> - - <!-- if sdk.dir was not set from one of the property file, then - get it from the ANDROID_HOME env var. - This must be done before we load project.properties since - the proguard config can use sdk.dir --> - <property environment="env" /> - <condition property="sdk.dir" value="${env.ANDROID_HOME}"> - <isset property="env.ANDROID_HOME" /> - </condition> - - <!-- The project.properties file is created and updated by the 'android' - tool, as well as ADT. - - This contains project specific properties such as project target, and library - dependencies. Lower level build properties are stored in ant.properties - (or in .classpath for Eclipse projects). - - This file is an integral part of the build system for your - application and should be checked into Version Control Systems. --> - <loadproperties srcFile="project.properties" /> - - <!-- quick check on sdk.dir --> - <fail - message="sdk.dir is missing. Make sure to generate local.properties using 'android update project' or to inject it through the ANDROID_HOME environment variable." - unless="sdk.dir" - /> - - <!-- - Import per project custom build rules if present at the root of the project. - This is the place to put custom intermediary targets such as: - -pre-build - -pre-compile - -post-compile (This is typically used for code obfuscation. - Compiled code location: ${out.classes.absolute.dir} - If this is not done in place, override ${out.dex.input.absolute.dir}) - -post-package - -post-build - -pre-clean - --> - <import file="custom_rules.xml" optional="true" /> - - <!-- Import the actual build file. - - To customize existing targets, there are two options: - - Customize only one target: - - copy/paste the target into this file, *before* the - <import> task. - - customize it to your needs. - - Customize the whole content of build.xml - - copy/paste the content of the rules files (minus the top node) - into this file, replacing the <import> task. - - customize to your needs. - - *********************** - ****** IMPORTANT ****** - *********************** - In all cases you must update the value of version-tag below to read 'custom' instead of an integer, - in order to avoid having your file be overridden by tools such as "android update project" - --> - <!-- version-tag: 1 --> - <import file="${sdk.dir}/tools/ant/build.xml" /> - -</project> diff --git a/testapps/libsTest/lib2Test/proguard-project.txt b/testapps/libsTest/lib2Test/proguard-project.txt deleted file mode 100644 index f2fe1559a..000000000 --- a/testapps/libsTest/lib2Test/proguard-project.txt +++ /dev/null @@ -1,20 +0,0 @@ -# To enable ProGuard in your project, edit project.properties -# to define the proguard.config property as described in that file. -# -# Add project specific ProGuard rules here. -# By default, the flags in this file are appended to flags specified -# in ${sdk.dir}/tools/proguard/proguard-android.txt -# You can edit the include path and order by changing the ProGuard -# include property in project.properties. -# -# For more details, see -# http://developer.android.com/guide/developing/tools/proguard.html - -# Add any project specific keep options here: - -# If your project uses WebView with JS, uncomment the following -# and specify the fully qualified class name to the JavaScript interface -# class: -#-keepclassmembers class fqcn.of.javascript.interface.for.webview { -# public *; -#} diff --git a/testapps/libsTest/lib2Test/project.properties b/testapps/libsTest/lib2Test/project.properties deleted file mode 100644 index dfe40b0c8..000000000 --- a/testapps/libsTest/lib2Test/project.properties +++ /dev/null @@ -1,16 +0,0 @@ -# This file is automatically generated by Android Tools. -# Do not modify this file -- YOUR CHANGES WILL BE ERASED! -# -# This file must be checked in Version Control Systems. -# -# To customize properties used by the Ant build system edit -# "ant.properties", and override values to adapt the script to your -# project structure. -# -# To enable ProGuard to shrink and obfuscate your code, uncomment this (available properties: sdk.dir, user.home): -#proguard.config=${sdk.dir}/tools/proguard/proguard-android.txt:proguard-project.txt - -# Project target. -target=android-15 -android.library.reference.1=../lib2 -manifestmerger.enabled=true diff --git a/testapps/libsTest/lib2Test/res/values/strings.xml b/testapps/libsTest/lib2Test/res/values/strings.xml deleted file mode 100644 index 68ce7718b..000000000 --- a/testapps/libsTest/lib2Test/res/values/strings.xml +++ /dev/null @@ -1,6 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<resources> - - <string name="lib2_name">LibsTest-lib2Test</string> - -</resources>
\ No newline at end of file diff --git a/testapps/libsTest/lib2Test/src/com/android/tests/libstest/lib2/MainActivityTest.java b/testapps/libsTest/lib2Test/src/com/android/tests/libstest/lib2/MainActivityTest.java deleted file mode 100644 index 6ac4a5c54..000000000 --- a/testapps/libsTest/lib2Test/src/com/android/tests/libstest/lib2/MainActivityTest.java +++ /dev/null @@ -1,86 +0,0 @@ -/* - * Copyright (C) 2008 The Android Open Source Project - * - * Licensed under the Apache License, Version 2.0 (the "License"); - * you may not use this file except in compliance with the License. - * You may obtain a copy of the License at - * - * http://www.apache.org/licenses/LICENSE-2.0 - * - * Unless required by applicable law or agreed to in writing, software - * distributed under the License is distributed on an "AS IS" BASIS, - * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - * See the License for the specific language governing permissions and - * limitations under the License. - */ - -package com.android.tests.libstest.lib2; - -import android.test.ActivityInstrumentationTestCase2; -import android.test.suitebuilder.annotation.MediumTest; -import android.widget.TextView; - -import com.android.tests.libstest.lib2.R; - -/** - * An example of an {@link ActivityInstrumentationTestCase2} of a specific activity {@link Focus2}. - * By virtue of extending {@link ActivityInstrumentationTestCase2}, the target activity is automatically - * launched and finished before and after each test. This also extends - * {@link android.test.InstrumentationTestCase}, which provides - * access to methods for sending events to the target activity, such as key and - * touch events. See {@link #sendKeys}. - * - * In general, {@link android.test.InstrumentationTestCase}s and {@link ActivityInstrumentationTestCase2}s - * are heavier weight functional tests available for end to end testing of your - * user interface. When run via a {@link android.test.InstrumentationTestRunner}, - * the necessary {@link android.app.Instrumentation} will be injected for you to - * user via {@link #getInstrumentation} in your tests. - * - * See {@link com.example.android.apis.AllTests} for documentation on running - * all tests and individual tests in this application. - */ -public class MainActivityTest extends ActivityInstrumentationTestCase2<MainActivity> { - - private TextView mTextView1; - private TextView mTextView2; - - /** - * Creates an {@link ActivityInstrumentationTestCase2} that tests the {@link Focus2} activity. - */ - public MainActivityTest() { - super(MainActivity.class); - } - - @Override - protected void setUp() throws Exception { - super.setUp(); - final MainActivity a = getActivity(); - // ensure a valid handle to the activity has been returned - assertNotNull(a); - - mTextView1 = (TextView) a.findViewById(R.id.lib2_text1); - mTextView2 = (TextView) a.findViewById(R.id.lib2_text2); - } - - /** - * The name 'test preconditions' is a convention to signal that if this - * test doesn't pass, the test case was not set up properly and it might - * explain any and all failures in other tests. This is not guaranteed - * to run before other tests, as junit uses reflection to find the tests. - */ - @MediumTest - public void testPreconditions() { - assertNotNull(mTextView1); - assertNotNull(mTextView2); - } - - @MediumTest - public void testAndroidStrings() { - assertEquals("SUCCESS-LIB2", mTextView1.getText()); - } - - @MediumTest - public void testJavaStrings() { - assertEquals("SUCCESS-LIB2", mTextView2.getText()); - } -} |