Runner 1.0.0 reports no tests with wiremock and/or assertj [64525881]

Fixed

Bug

Status Update

No update yet.

Description

ma...@gmail.com

created issue #1

Aug 9, 2017 05:53PM

Using the Android Runner 1.0.0 with Wiremock or Assetj will report no tests found while using the 0.5 version will work as expected.

Library used (Espresso, Runner, Rules etc.): Runner
Version used: 1.0.0

What steps will reproduce the problem?
See project here:

https://github.com/marcuspridham/android_runner_issue

How are you running your tests (via Android Studio, Gradle, adb, etc.)?
Gradle

What is the expected output? What do you see instead?
Test should be found and run but instead a No tests found error is reported. Using the 0.5 version of runner successfully executes the tests. This appears to be a regression between 0.5 and 1.0.0.

Comments

nk...@google.com <nk...@google.com> Aug 17, 2017 01:38AM

Assigned to nk...@google.com.

nk...@google.com <nk...@google.com> #2Aug 17, 2017 05:24PM

Marked as fixed.

Might be related to

https://issuetracker.google.com/issues/118020865. BTW, I'm using 1.1.0-alpha01.

Project:

https://github.com/SUPERCILEX/Robot-Scouter/tree/2e3100276e5fe2cbad8a2cbb36303694e9f46bbd
Setup: ./gradlew setup

nk...@google.com <nk...@google.com> #3Aug 23, 2017 06:34PM

This is due to a bug in Fragment - using 1.1.0-alpha02 of Preference uses a newer Fragment dependency, and fixes this issue.

ma...@gmail.com <ma...@gmail.com> #4Aug 23, 2017 09:56PM

Actually, I just checked and it still crashes using 1.1.0-alpha02.

Issue 64525881

Description

Issue summary

Comments

nk...@google.com <nk...@google.com> Aug 17, 2017 01:38AM

nk...@google.com <nk...@google.com> #2Aug 17, 2017 05:24PM

nk...@google.com <nk...@google.com> #3Aug 23, 2017 06:34PM

ma...@gmail.com <ma...@gmail.com> #4Aug 23, 2017 09:56PM

Add comment

Issue metadata