ActivityInstrumentationTestCase2研究成果
来源:互联网 发布:java主方法调用 编辑:程序博客网 时间:2024/04/28 10:16
准备打算做一点android平台下的自动化测试,代码写好后准备进行自动化,发现自己对ActivityInstrumentationTestCase2还一点点都不太了解,不得已又返回来了解ActivityInstrumentationTestCase2的一些知识,以便后面更好的进行android平台下自动化框架的搭建和学习。
ActivityInstrumentationTestCase2
extends ActivityTestCaseClass Overview
This class provides functional testing of a single activity. The activity under test will be created using the system infrastructure (by calling InstrumentationTestCase.launchActivity()) and you will then be able to manipulate your Activity directly.
Other options supported by this test case include:
- You can run any test method on the UI thread (see
UiThreadTest
). - You can inject custom Intents into your Activity (see
setActivityIntent(Intent)
).
This class replaces ActivityInstrumentationTestCase
, which is deprecated. New tests should be written using this base class.
If you prefer an isolated unit test, see ActivityUnitTestCase
.
Developer Guides
For more information about application testing, read the Testing developer guide.
Summary
ActivityInstrumentationTestCase2(Class)
insteadActivityInstrumentationTestCase2
.getActivity()
to set the initial touch mode for the Activity under test.getActivity()
to inject a customized Intent into the Activity under test.Public Constructors
public ActivityInstrumentationTestCase2 (String pkg, Class<T> activityClass)
This constructor is deprecated.
use ActivityInstrumentationTestCase2(Class)
instead
Creates an ActivityInstrumentationTestCase2
.
Parameters
public ActivityInstrumentationTestCase2 (Class<T> activityClass)
Creates an ActivityInstrumentationTestCase2
.
Parameters
Public Methods
public T getActivity ()
Get the Activity under test, starting it if necessary. For each test method invocation, the Activity will not actually be created until the first time this method is called.
If you wish to provide custom setup values to your Activity, you may call setActivityIntent(Intent)
and/or setActivityInitialTouchMode(boolean)
before your first call to getActivity(). Calling them after your Activity has started will have no effect.
NOTE: Activities under test may not be started from within the UI thread. If your test method is annotated with UiThreadTest
, then your Activity will be started automatically just before your test method is run. You still call this method in order to get the Activity under test.
Returns
- the Activity under test
public void setActivityInitialTouchMode (boolean initialTouchMode)
Call this method before the first call to getActivity()
to set the initial touch mode for the Activity under test.
If you do not call this, the touch mode will be false. If you call this after your Activity has been started, it will have no effect.
NOTE: Activities under test may not be started from within the UI thread. If your test method is annotated with UiThreadTest
, then you must call setActivityInitialTouchMode(boolean)
fromsetUp()
.
Parameters
public void setActivityIntent (Intent i)
Call this method before the first call to getActivity()
to inject a customized Intent into the Activity under test.
If you do not call this, the default intent will be provided. If you call this after your Activity has been started, it will have no effect.
NOTE: Activities under test may not be started from within the UI thread. If your test method is annotated with UiThreadTest
, then you must call setActivityIntent(Intent)
from setUp()
.
The default Intent (if this method is not called) is: action = ACTION_MAIN
flags = FLAG_ACTIVITY_NEW_TASK
All other fields are null or empty.
Parameters
Protected Methods
protected void runTest ()
Runs the current unit test. If the unit test is annotated with UiThreadTest
, force the Activity to be created before switching to the UI thread.
Throws
protected void setUp ()
Sets up the fixture, for example, open a network connection. This method is called before a test is executed.
Throws
protected void tearDown ()
Make sure all resources are cleaned up and garbage collected before moving on to the next test. Subclasses that override this method should make sure they call super.tearDown() at the end of the overriding method.
Throws
- ActivityInstrumentationTestCase2研究成果
- ActivityInstrumentationTestCase2类
- androidpn研究成果
- MAXIMO研究成果
- androidpn研究成果
- androidpn研究成果
- 利用ActivityInstrumentationTestCase2测试Activity
- activityinstrumentationtestcase2 排坑
- android的ActivityInstrumentationTestCase2测试
- android代码测试界面 ( ActivityInstrumentationTestCase2 )
- FusionCharts之研究成果
- 数据库安全防护研究成果
- 【转】androidpn研究成果
- 今天的研究成果
- 消息推送_androidpn_androidpn研究成果
- opendns安全研究成果
- 2017最新研究成果SIGIR
- Android测试教程(10):ActivityInstrumentationTestCase2示例
- CANOpen的几种操作以及数据
- Linux进程的实际用户ID和有效用户ID
- PYTHON循环(列表,字典)
- NPOI实现excel 2003 在线审批签字功能,缺陷不知如何进行工作簿保护?求解
- Qt开发:释放线程中创建的QUdpSocket对象
- ActivityInstrumentationTestCase2研究成果
- Struts知识点总结
- Android HAL(硬件抽象层)介绍以及调用
- 传智播客——毕向东25--第5天总结-4
- 读书笔记-----类继承
- cdt error while loading shared libraries stackover
- java foreach语法 的ConcurrentModificationException 异常
- Java创建线程的两个方法
- Android学习笔记:根据系列图片绘制动画总结