You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 7, 2019. It is now read-only.
Runner v0.5 printed that as instrumentation problem but continued to run tests (that was not perfect, but better behavior), Runner v1.0 fails test run.
Firebase Test Cloud happily marks test run as successful in both cases even though in fact in second case none of the tests did actually run.
That's why I'm creating this issue against Composer to make sure (add test) that following instrumentation output will cause error in Composer and test run won't be marked as successful.
Composer already fails test run if 0 tests were run, but I just want make code even more robust against such stupid errors and be better than Firebase at parsing Google's crazy instrumentation output format.
The text was updated successfully, but these errors were encountered:
AndroidJUnitRunner
from test support library v1.0 fails test run if app or test apk references non-existing classes. See https://issuetracker.google.com/u/1/issues/64094195Runner v0.5 printed that as instrumentation problem but continued to run tests (that was not perfect, but better behavior), Runner v1.0 fails test run.
Firebase Test Cloud happily marks test run as successful in both cases even though in fact in second case none of the tests did actually run.
That's why I'm creating this issue against Composer to make sure (add test) that following instrumentation output will cause error in Composer and test run won't be marked as successful.
Composer already fails test run if 0 tests were run, but I just want make code even more robust against such stupid errors and be better than Firebase at parsing Google's crazy instrumentation output format.
The text was updated successfully, but these errors were encountered: