使用Android CTS工具执行所有测试需要多少时间?

发布于 2024-11-27 06:34:46 字数 197 浏览 1 评论 0原文

我正在开发自定义 Android 设备,需要使用 Android CTS 工具 执行兼容性测试用例。

所以我只想知道使用android-cts-2.3_r3-x86工具android设备(Android模拟器)上执行所有测试用例需要多长时间。

I am developing custom android device and need to execute compatibility test cases using android CTS tool.

So i just want to know how much time it will take to execute all the test cases on the android device(Android Emulator) using android-cts-2.3_r3-x86 tool.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

蓝天白云 2024-12-04 06:34:46

CTS的执行时间取决于测试用例的总数和测试用例结果的每个状态。为了通过测试,大多数测试用例的结果必须在 5 秒内得出,否则测试用例就会超时。每次超时后,CTS 都会有 5 分钟的间隔来执行下一个测试用例。所以它与超时测试用例的数量成正比。设备多次重启,因此重启时间也被计算在内。现在您可以计算CTS执行的预计时间。

The time for execution of CTS depends upon the total number of test cases and each status of the test case result. To pass a test the result must come in 5 seconds for most of test cases, otherwise the test cases is timed out. After each time out there is a gap of 5 minutes to execute next test case by CTS. So it is directly proportional to the number of timed out test cases. Many time the devices restarts, so the restart time is also counted. Now you can calculate the estimated time of CTS execution.

空心↖ 2024-12-04 06:34:46

通常,它会在测试开始时显示估计值,如上面的示例所示:

255522-06-07 14:32:23 I/CompatibilityTest: ========================================
255599:06-07 14:32:23 I/CompatibilityTest: Starting a run with 362 unique modules.
255675-06-07 14:32:23 I/CompatibilityTest: ========================================
255752-06-07 14:32:23 I/ModuleRepo: 10.10.1.113:5555 running 362 test sub-modules, expected to complete in 86h 46m 18s.

如果您丢失了,这不是问题,您可以随时使用 cts-tf > 光标中的命令检查日志:

d l

转储日志 的快捷方式将输出:

Saved log to /tmp/Invocation-134.86.122.113:5555_log_7887452889537372588.txt
Saved log to /tmp/tradefed_history_log_6569426154219158581.txt
Saved log to /tmp/tradefed_global_log_802202482888218382.txt

然后在日志中 grep 查找唯一的和 2 行:

cat ./Invocation-134.86.122.113:5555_log_3749453462240679705.txt | grep unique -b2

Usually it is displayed an estimation at the beginning of the tests, like in the above example:

255522-06-07 14:32:23 I/CompatibilityTest: ========================================
255599:06-07 14:32:23 I/CompatibilityTest: Starting a run with 362 unique modules.
255675-06-07 14:32:23 I/CompatibilityTest: ========================================
255752-06-07 14:32:23 I/ModuleRepo: 10.10.1.113:5555 running 362 test sub-modules, expected to complete in 86h 46m 18s.

if you lost that is not a problem you can always check the logs with the command in cts-tf > cursor:

d l

shortcut for dump logs will output:

Saved log to /tmp/Invocation-134.86.122.113:5555_log_7887452889537372588.txt
Saved log to /tmp/tradefed_history_log_6569426154219158581.txt
Saved log to /tmp/tradefed_global_log_802202482888218382.txt

and then grep in the logs for unique and 2 lines:

cat ./Invocation-134.86.122.113:5555_log_3749453462240679705.txt | grep unique -b2
梦在深巷 2024-12-04 06:34:46

我几乎花了 2 个小时在 SHIELD 上运行完整的测试集。测试结果:
- 通过:9805
- 失败:7
- 未执行:8977

This took me almost exactly 2 hours to run the full test set on a SHIELD. The results of tests:
- PASSED: 9805
- FAILED: 7
- NOT EXECUTED: 8977

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文