TestInvocation

/**
* {@inheritDoc}
*/
@Override
public void invoke(ITestDevice device, IConfiguration config, IRescheduler rescheduler) throws DeviceNotAvailableException, Throwable {
try {
mStatus = "fetching build";
config.getLogOutput().init();
getLogRegistry().registerLogger(config.getLogOutput());
IBuildInfo info = null;
if (config.getBuildProvider() instanceof IDeviceBuildProvider) {
info = ((IDeviceBuildProvider) config.getBuildProvider()).getBuild(device);
} else if (config.getBuildProvider() instanceof IDeviceConfigBuildProvider) {
// 调用config获得cts.xml文件里的<build_provider>标签中相应的类,然后通过调用getBuild得到IBuildInfo对象
info = ((IDeviceConfigBuildProvider) config.getBuildProvider()).getBuild(device, config);
} else {
info = config.getBuildProvider().getBuild();
}
if (info != null) {
// System.out.println(String.format("setup: %s tearDown: %s",
// config.getCommandOptions().isNeedPrepare(),
// config.getCommandOptions().isNeedTearDown()));
CLog.logAndDisplay(LogLevel.INFO,
String.format("setup: %s tearDown: %s", config.getCommandOptions().isNeedPrepare(), config.getCommandOptions().isNeedTearDown()));
// 获取<test>配置项里的測试选项,并注入到info中
injectBuild(info, config.getTests());
if (shardConfig(config, info, rescheduler)) {
CLog.i("Invocation for %s has been sharded, rescheduling", device.getSerialNumber());
} else {
device.setRecovery(config.getDeviceRecovery());
// 准备刷机,启动case
performInvocation(config, device, info, rescheduler);
// exit here, depend on performInvocation to deregister
// logger
return;
}
} else {
mStatus = "(no build to test)";
CLog.d("No build to test");
rescheduleTest(config, rescheduler);
}
} catch (BuildRetrievalError e) {
CLog.e(e);
/*
* because this is BuildRetrievalError, so do not generate test
* result // report an empty invocation, so this error is sent to
* listeners startInvocation(config, device, e.getBuildInfo()); //
* don't want to use #reportFailure, since that will call
* buildNotTested for (ITestInvocationListener listener :
* config.getTestInvocationListeners()) {
* listener.invocationFailed(e); } reportLogs(device,
* config.getTestInvocationListeners(), config.getLogOutput());
* InvocationSummaryHelper.reportInvocationEnded(
* config.getTestInvocationListeners(), 0); return;
*/
} catch (IOException e) {
CLog.e(e);
}
// save current log contents to global log
getLogRegistry().dumpToGlobalLog(config.getLogOutput());
getLogRegistry().unregisterLogger();
config.getLogOutput().closeLog();
}

之所以称为调度室,由于它就是去一步一步的执行9大组件的剩余组件,组件与组件之间并不知道对方的存在,仅仅有TestInvocation自己知道。它通过反射的机制到的对象,别创建对象,然后调用当中的接口方法得到它想要的,然后再传给下一个组件。以上方法就能够看出,它先得到buildprovider对象。调用getBuild对象得到IBuildInfo对象。咱们这个程序中,事实上就是调用了CtsBuildProvider的getBuild方法。

假设info不为null:然后给測试任务注入IBuildInfo,推断能否够分拆任务,假设不能分拆的话,注冊设备恢复类,然后跳转到performInvocation方法中。

假设info为null:提示没有可运行的build,调用IRescheduler.rescheduleCommand()重试。

/**
* Performs the invocation
*
* @param config
* the {@link IConfiguration}
* @param device
* the {@link ITestDevice} to use. May be <code>null</code>
* @param info
* the {@link IBuildInfo}
*/
private void performInvocation(IConfiguration config, ITestDevice device, IBuildInfo info, IRescheduler rescheduler) throws Throwable { boolean resumed = false;
long startTime = System.currentTimeMillis();
long elapsedTime = -1; info.setDeviceSerial(device.getSerialNumber());
startInvocation(config, device, info);
try {
device.setOptions(config.getDeviceOptions());
// 准备build和跑case
prepareAndRun(config, device, info, rescheduler);
} catch (BuildError e) {
CLog.w("Build %s failed on device %s. Reason: %s", info.getBuildId(), device.getSerialNumber(), e.toString());
takeBugreport(device, config.getTestInvocationListeners(), BUILD_ERROR_BUGREPORT_NAME);
reportFailure(e, config.getTestInvocationListeners(), config, info, rescheduler);
} catch (TargetSetupError e) {
CLog.e("Caught exception while running invocation");
CLog.e(e);
reportFailure(e, config.getTestInvocationListeners(), config, info, rescheduler);
// maybe test device if offline, check it
device.waitForDeviceOnline();
} catch (DeviceNotAvailableException e) {
// log a warning here so its captured before reportLogs is called
CLog.w("Invocation did not complete due to device %s becoming not available. " + "Reason: %s", device.getSerialNumber(), e.getMessage());
if ((e instanceof DeviceUnresponsiveException) && TestDeviceState.ONLINE.equals(device.getDeviceState())) {
// under certain cases it might still be possible to grab a
// bugreport
takeBugreport(device, config.getTestInvocationListeners(), DEVICE_UNRESPONSIVE_BUGREPORT_NAME);
}
resumed = resume(config, info, rescheduler, System.currentTimeMillis() - startTime);
if (!resumed) {
reportFailure(e, config.getTestInvocationListeners(), config, info, rescheduler);
} else {
CLog.i("Rescheduled failed invocation for resume");
}
throw e;
} catch (RuntimeException e) {
// log a warning here so its captured before reportLogs is called
CLog.w("Unexpected exception when running invocation: %s", e.toString());
reportFailure(e, config.getTestInvocationListeners(), config, info, rescheduler);
throw e;
} catch (AssertionError e) {
CLog.w("Caught AssertionError while running invocation: ", e.toString());
reportFailure(e, config.getTestInvocationListeners(), config, info, rescheduler);
} finally {
mStatus = "done running tests";
try {
//
reportLogs(device, config.getTestInvocationListeners(), config.getLogOutput());
elapsedTime = System.currentTimeMillis() - startTime;
if (!resumed) {
// 发送报告
InvocationSummaryHelper.reportInvocationEnded(config.getTestInvocationListeners(), elapsedTime);
} } finally {
config.getBuildProvider().cleanUp(info);
}
}
}

首先启动全部监听器的start方法,起一个通知開始的作用。

/**
* Starts the invocation.
* <p/>
* Starts logging, and informs listeners that invocation has been started.
*
* @param config
* @param device
* @param info
*/
private void startInvocation(IConfiguration config, ITestDevice device, IBuildInfo info) {
logStartInvocation(info, device);
for (ITestInvocationListener listener : config.getTestInvocationListeners()) {
try {
listener.invocationStarted(info);
} catch (RuntimeException e) {
// don't let one listener leave the invocation in a bad state
CLog.e("Caught runtime exception from ITestInvocationListener");
CLog.e(e);
}
}
}

然后得到device_options对象,设置到ITestDevice中。再调用prepareAndRun(config, device, info, rescheduler);方法。

private void prepareAndRun(IConfiguration config, ITestDevice device, IBuildInfo info, IRescheduler rescheduler) throws Throwable {
// use the JUnit3 logic for handling exceptions when running tests
Throwable exception = null; try {
//
if (config.getCommandOptions().isNeedPrepare()&&!isRepeat) {
doSetup(config, device, info);
//下次启动的时候,不再刷机
isRepeat = true;
}else{
CLog.logAndDisplay(LogLevel.DEBUG, String.format("No need to flash,derect to run case"));
}
// 跑case
runTests(device, info, config, rescheduler);
} catch (Throwable running) {
exception = running;
} finally {
try {
if (config.getCommandOptions().isNeedTearDown()) {
doTeardown(config, device, info, exception);
}
} catch (Throwable tearingDown) {
if (exception == null) {
exception = tearingDown;
}
}
}
if (exception != null) {
throw exception;
}
}

在该方法中先得到依据cmd_options得到是否须要prepare,假设须要,就调用target_prepare类来做准备工作,假设不须要,直接调用runTests方法

private void runTests(ITestDevice device, IBuildInfo buildInfo, IConfiguration config, IRescheduler rescheduler) throws DeviceNotAvailableException {
List<ITestInvocationListener> listeners = config.getTestInvocationListeners();
for (IRemoteTest test : config.getTests()) {
if (test instanceof IDeviceTest) {
((IDeviceTest) test).setDevice(device);
}
test.run(new ResultForwarder(listeners));
}
}

上面的方法调用tests配置的类来追个调用里面的run方法启动測试。測试完毕后,来做tearDown的工作。

Cts框架解析(7)-任务运行的调度室的更多相关文章

  1. Cts框架解析(15)-任务运行完

    case运行完成后.会回到CtsTest的run方法中: watermark/2/text/aHR0cDovL2Jsb2cuY3Nkbi5uZXQvaXRmb290YmFsbA==/font/5a6L ...

  2. Cts框架解析(2)-cts调试环境的搭建

    上一篇文章中说了怎样在windows搭建cts以及执行cts进行測试.这篇文章来讲讲怎样在eclipse中配置源代码,进行debug调试. 下载 cts源代码地址:https://android.go ...

  3. Cts框架解析(6)-任务的运行

    前两篇讲了任务的加入和9大项配置,这篇讲任务的运行. 任务的运行 任务的运行在CommandScheduler的run方法中,所以删除全部的断点,在run方法中打上断点,重新启动启动debug: 先看 ...

  4. Cts框架解析(1)-windows下cts配置

    环境搭建 下载 cts工具的下载地址:http://source.android.com/compatibility/downloads.html windows选择Android4.4 R3 Com ...

  5. Cts框架解析(8)-IBuildProvider

    IBuildProvider接口中定义了三个方法 /* * Copyright (C) 2010 The Android Open Source Project * * Licensed under ...

  6. Cts框架解析(12)-ITargetPreparer

    測试开启前的设备系统准备工作. 接口 /* * Copyright (C) 2010 The Android Open Source Project * * Licensed under the Ap ...

  7. [转载]iOS 10 UserNotifications 框架解析

    活久见的重构 - iOS 10 UserNotifications 框架解析 TL;DR iOS 10 中以前杂乱的和通知相关的 API 都被统一了,现在开发者可以使用独立的 UserNotifica ...

  8. iOS 10 UserNotifications 框架解析

    摘自:https://onevcat.com/2016/08/notification/ iOS 10 中以前杂乱的和通知相关的 API 都被统一了,现在开发者可以使用独立的 UserNotifica ...

  9. Poco::TCPServer框架解析

    Poco::TCPServer框架解析 POCO C++ Libraries提供一套 C++ 的类库用以开发基于网络的可移植的应用程序,功能涉及线程.文件.流,网络协议包括:HTTP.FTP.SMTP ...

随机推荐

  1. python学习笔记--for循环

    推荐一个学习语言的网站:http://www.codecademy.com 有教程,可以边学边写,蛮不错的. for循环: 1.for loops allow us to iterate throug ...

  2. 从PCI上读取数据 线程和定时器效率

    从PCI上读取数据 线程和定时器效率 线程: mythread=AfxBeginThread(StartContinuous,(LPVOID)1,THREAD_PRIORITY_NORMAL,0,CR ...

  3. 九度 题目1044:Pre-Post

    转载请注明本文链接http://blog.csdn.net/yangnanhai93/article/details/40658571 题目链接:pid=1044">http://ac ...

  4. 不root的情况下 查看App的数据表

    一直以来查看sqlite的数据库都须要root才干查看,可是公司的好多測试机root起来比較麻烦~~~ 近期刚好项目上线,略闲, 于是决定写一个libraryproject便于以后调试代码 关键代码例 ...

  5. 分解XML方法

    分解XML方法 1.DOM生成和解析XML 2.SAX生成和解析XML 3.DOM4J生成和解析XML 4.JDOM生成和解析XML 版权声明:本文博主原创文章.博客,未经同意不得转载.

  6. Cocos2d-x 脚本语言Lua中的面向对象

    Cocos2d-x 脚本语言Lua中的面向对象 面向对象不是针对某一门语言,而是一种思想.在面向过程的语言也能够使用面向对象的思想来进行编程. 在Lua中,并没有面向对象的概念存在,没有类的定义和子类 ...

  7. hdu 4557 非诚勿扰 vector的应用 原来vector 可以删除指定位置元素 不过消耗大

    非诚勿扰 Time Limit: 3000/1000 MS (Java/Others)    Memory Limit: 65535/32768 K (Java/Others) Total Submi ...

  8. PL/SQL 游标的使用

     游标的使用 ①游标概念 为了处理SQL 语句,ORACLE 必须分配一片叫上下文( context area )的区域来处理所必需的信息, 当中包含要处理的行的数目.一个指向语句被分析以后的表示 ...

  9. 三白话经典算法系列 Shell排序实现

    山是包插入的精髓排序排序,这种方法,也被称为窄增量排序.因为DL.Shell至1959提出命名. 该方法的基本思想是:先将整个待排元素序列切割成若干个子序列(由相隔某个"增量"的元 ...

  10. git tag使用

    #git tag command git tag [-a | -s | -u <key-id>] [-f] [-m <msg> | -F <file>]       ...