blocks|key|2877281|text|连接的测试将输出和事件记录到logcat，因为它在设备/仿真器上运行。测试事件记录在TestRunner标签下。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2877282|我使用以下脚本在后台启动adb+logcat，在执行测试时记录TestRunner事件，然后终止logcat进程。|2877283|adb+logcat+*:S+TestRunner:V+&+LOGCAT_PID=$!+;+\
./gradlew+:app:cAT+;+\
if+[+-n+"$LOGCAT_PID"+]+;+then+kill+$LOGCAT_PID;+fi|code-block|syntax|javascript|2877284|它会产生类似下面这样的结果：|2877285|[1]+90439
---------+beginning+of+system
---------+beginning+of+main
:app:preBuild+UP-TO-DATE
:app:preDebugBuild+UP-TO-DATE
...
:app:packageDebugAndroidTest+UP-TO-DATE
:app:assembleDebugAndroidTest+UP-TO-DATE
>+Building+96%25+>+:app:connectedDebugAndroidTest06-13+09:25:04.259++5460++5474+I+TestRunner:+run+started:+23+tests
06-13+09:25:04.267++5460++5474+I+TestRunner:+started:+testHomeClick(io.github.hidroh.tldroid.CommandActivityTest)
06-13+09:25:06.899++5460++5474+I+TestRunner:+finished:+testHomeClick(io.github.hidroh.tldroid.CommandActivityTest)
06-13+09:25:06.903++5460++5474+I+TestRunner:+started:+testRenderNoContent(io.github.hidroh.tldroid.CommandActivityTest)
06-13+09:25:08.128++5460++5474+I+TestRunner:+finished:+testRenderNoContent(io.github.hidroh.tldroid.CommandActivityTest)
06-13+09:25:08.130++5460++5474+I+TestRunner:+started:+testStateRestoration(io.github.hidroh.tldroid.CommandActivityTest)
06-13+09:25:09.547++5460++5474+I+TestRunner:+finished:+testStateRestoration(io.github.hidroh.tldroid.CommandActivityTest)
...
06-13+09:25:35.283++5460++5474+I+TestRunner:+run+finished:+23+tests,+0+failed,+0+ignored
:app:connectedDebugAndroidTest
:app:createDebugAndroidTestCoverageReport
:app:connectedAndroidTest

BUILD+SUCCESSFUL

Total+time:+1+mins+7.485+secs
[1]%2B++Terminated:+15++++++++++adb+logcat+*:S+TestRunner:V|2877286|当然，您可以调整logcat命令以使用您选择的记录器，例如颜色记录器，或者更改logcat+filterspec以显示更多事件。|2877287|entityMap^0|E|6|16|A|0|C|A|V|A|1C|6|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]|$9|14|A|15|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|16|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|17|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|18|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|19|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|T|$]]

Connected tests log output and events to <code>logcat</code>, as it runs on a device/emulator. Test events are logged under <code>TestRunner</code> tag.

I use the following script to start <code>adb logcat</code> in the background, which logs <code>TestRunner</code> events as tests are being executed, and kill the <code>logcat</code> process afterwards.

<pre><code>adb logcat *:S TestRunner:V &amp; LOGCAT_PID=$! ; \
./gradlew :app:cAT ; \
if [ -n "$LOGCAT_PID" ] ; then kill $LOGCAT_PID; fi
</code></pre>

which produces something like this:

<pre><code>[1] 90439
--------- beginning of system
--------- beginning of main
:app:preBuild UP-TO-DATE
:app:preDebugBuild UP-TO-DATE
...
:app:packageDebugAndroidTest UP-TO-DATE
:app:assembleDebugAndroidTest UP-TO-DATE
&gt; Building 96% &gt; :app:connectedDebugAndroidTest06-13 09:25:04.259 5460 5474 I TestRunner: run started: 23 tests
06-13 09:25:04.267 5460 5474 I TestRunner: started: testHomeClick(io.github.hidroh.tldroid.CommandActivityTest)
06-13 09:25:06.899 5460 5474 I TestRunner: finished: testHomeClick(io.github.hidroh.tldroid.CommandActivityTest)
06-13 09:25:06.903 5460 5474 I TestRunner: started: testRenderNoContent(io.github.hidroh.tldroid.CommandActivityTest)
06-13 09:25:08.128 5460 5474 I TestRunner: finished: testRenderNoContent(io.github.hidroh.tldroid.CommandActivityTest)
06-13 09:25:08.130 5460 5474 I TestRunner: started: testStateRestoration(io.github.hidroh.tldroid.CommandActivityTest)
06-13 09:25:09.547 5460 5474 I TestRunner: finished: testStateRestoration(io.github.hidroh.tldroid.CommandActivityTest)
...
06-13 09:25:35.283 5460 5474 I TestRunner: run finished: 23 tests, 0 failed, 0 ignored
:app:connectedDebugAndroidTest
:app:createDebugAndroidTestCoverageReport
:app:connectedAndroidTest

BUILD SUCCESSFUL

Total time: 1 mins 7.485 secs
[1]+ Terminated: 15 adb logcat *:S TestRunner:V
</code></pre>

You can of course tweak logcat command to use a logger of your choice, e.g. a color logger, or change logcat filterspec to show more events.

blocks|key|2877296|text|最简单的版本就是使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2877297|信息。/gradlew+connectedAndroidTest+--+|2877298|blockquote|2877299|2877300|2877301|在终端/控制台窗口中记录它需要一点时间，但是它显示了所有漂亮的、彩色的和格式化的东西|2877302|像…一样|2877303|…ShowsIntroduction[SM-G950F+-+7.0]+SUCCESS+
…BackButtonReturnsToOnboardingScreen[SM-G950F+-+7.0]+SKIPPED|code-block|syntax|javascript|2877304|祝你好运&&玩得开心|2877305|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|-4|5|E|7|W|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Z|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|11|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|12|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|T|$]]

The easy version is just to use:

<blockquote>
 ./gradlew connectedAndroidTest --info
</blockquote>

it take a littlebit to log it in the terminal/console window, but it's showing everything nice, colored and formatted

like …

<pre><code>…ShowsIntroduction[SM-G950F - 7.0] SUCCESS 
…BackButtonReturnsToOnboardingScreen[SM-G950F - 7.0] SKIPPED
</code></pre>

good luck &amp;&amp; have fun

As explained in other threads Gradle can be configured to log test results into the console:

<ul>
<li><a href="https://stackoverflow.com/questions/30308435/gradle-android-how-to-display-test-results-without-using-info">Gradle Android: How to Display test results without using --info</a></li>
<li><a href="https://stackoverflow.com/questions/3963708/gradle-how-to-display-test-results-in-the-console-in-real-time">Gradle: How to Display Test Results in the Console in Real Time?</a></li>
<li><a href="https://stackoverflow.com/questions/24360099/output-unit-testing-results-on-console-using-spock-junit-testing-and-gradle-buil">Output unit testing results on console using spock junit testing and gradle build system</a></li>
</ul>

Basically, this can be setup through the following task:

<pre><code>tasks.withType(Test) {
 testLogging {
 // Custom configuration
 }
}
</code></pre>

This works fine for unit tests and looks somewhat like this:

<pre><code>...
:app:assembleDebugUnitTest
:app:testDebugUnitTest
:app:processDebugResources

com.example.StringsTest &gt; formatValue PASSED
com.example.StringsTest &gt; formatValueWithDecimals FAILED

1 test completed, 1 failed
</code></pre>

Besides, unit tests I also run integration test using the following command:

<pre><code>$ ./gradlew connectedAndroidTest
</code></pre>

When I look at the output in the console I am missing the individual test results as being written for unit tests. How can I configure test logging for instrumentation tests?

Gradle: How to display androidTest results in the console?

单元测试

集成测试

正如在其他线程中解释的那样，Gradle可以配置为将测试结果记录到控制台中：基本上，这可以通过以下任务进行设置：tasks.withType(Test) {    testLogging {       // Custom configuration    }}这对于单元测试很有效，看起来有点像这样：...:app:a...

问Gradle:如何在控制台显示androidTest结果？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Gradle:如何在控制台显示androidTest结果？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Gradle:如何在控制台显示androidTest结果？
EN