1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
|
/*
* 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.flavors;
import android.test.ActivityInstrumentationTestCase2;
import android.test.suitebuilder.annotation.MediumTest;
import android.widget.TextView;
/**
* 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 MainActivityGroup1Test extends ActivityInstrumentationTestCase2<MainActivity> {
private TextView mResOverLay;
private TextView mResOverLay1;
private TextView mBuildConfig1;
private TextView mCodeOverlay1;
/**
* Creates an {@link ActivityInstrumentationTestCase2} that tests the {@link Focus2} activity.
*/
public MainActivityGroup1Test() {
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);
mResOverLay = (TextView) a.findViewById(R.id.resoverlay);
mResOverLay1 = (TextView) a.findViewById(R.id.resoverlay1);
mBuildConfig1 = (TextView) a.findViewById(R.id.buildconfig1);
mCodeOverlay1 = (TextView) a.findViewById(R.id.codeoverlay1);
}
/**
* 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(mResOverLay);
assertNotNull(mResOverLay1);
assertNotNull(mBuildConfig1);
assertNotNull(mCodeOverlay1);
}
@MediumTest
public void testResOverlay() {
assertEquals("F1", mResOverLay.getText());
assertEquals("F1", mResOverLay1.getText());
}
@MediumTest
public void testBuildConfig() {
assertEquals("F1", mBuildConfig1.getText());
}
@MediumTest
public void testCodeOverlay() {
assertEquals("F1", mCodeOverlay1.getText());
}
}
|
