Bug P3
Status Update
No update yet.
Comments
vi...@google.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Device used -- Device Make, Model, Android OS Version
Which device did you use to reproduce this issue?
Please provide sample project (Instrumented test project) to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project.
Expected output
What is the expected output?
Current output
What is the current output?
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:https://developer.android.com/studio/debug/bug-report#bugreportdevice
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Screen Record of the Issue
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
Device used -- Device Make, Model, Android OS Version
Which device did you use to reproduce this issue?
Please provide sample project (Instrumented test project) to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project.
Expected output
What is the expected output?
Current output
What is the current output?
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Screen Record of the Issue
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
[Deleted User] <[Deleted User]>
Really, you guys shouldn't just copy and paste boiler plate responses asking questions that have *already* been answered. Then I don't know if you just didn't read the ticket or you really need more information? Adds to Google's already bad image of being careless and unresponsive to bug reports.
Anyways, despite you apparently not reading the ticket, I'll answer the questions as best I can:
> Which device did you use to reproduce this issue?
Samsung Galaxy Tab A (2019 model) running Android 9
> Please provide sample project (Instrumented test project) to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project.
Steps to reproduce have already been provided.
> Expected output
> What is the expected output?
Already provided.
> Current output
> What is the current output?
Already provided.
> Android bug report
There is no crash, so this makes no sense to me. What are you looking for?
> Screen Record of the Issue
Not something you can see on the screen.
Anyways, despite you apparently not reading the ticket, I'll answer the questions as best I can:
> Which device did you use to reproduce this issue?
Samsung Galaxy Tab A (2019 model) running Android 9
> Please provide sample project (Instrumented test project) to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project.
Steps to reproduce have already been provided.
> Expected output
> What is the expected output?
Already provided.
> Current output
> What is the current output?
Already provided.
> Android bug report
There is no crash, so this makes no sense to me. What are you looking for?
> Screen Record of the Issue
Not something you can see on the screen.
vi...@google.com
Moving issue to androidx >Test component to check this issue.
ae...@google.com
This bug has not been updated in the last year. Please reopen if we still need to look into this.
Description
Steps to Reproduce:
Build an Instrumented test that will fail (ClassNotFoundException or other) in the @BeforeClass or during an @Mock. The log output will be something like:
[exec] 01:47:10 V/InstrumentationResultParser: There was 1 failure:
[exec] 01:47:10 V/InstrumentationResultParser: 1) com.hcs.android.orconnect.ui.bindings.ButtonBindingsTest
[exec] 01:47:10 V/InstrumentationResultParser: java.util.ServiceConfigurationError: com.hcs.orc.command.provider.CommandFactoryProvider: Provider com.hcs.orc.command.ORConnectCommandFactory not found
....
[exec] 01:47:10 V/InstrumentationResultParser: Caused by: java.lang.ClassNotFoundException: com.hcs.orc.command.ORConnectCommandFactory
....
[exec] 01:47:10 V/InstrumentationResultParser: FAILURES!!!
[exec] 01:47:10 V/InstrumentationResultParser: Tests run: 32, Failures: 1
[exec] 01:47:10 V/InstrumentationResultParser:
[exec] 01:47:10 V/InstrumentationResultParser:
[exec] 01:47:10 V/InstrumentationResultParser: INSTRUMENTATION_CODE: -1
[exec] 01:47:10 V/InstrumentationResultParser:
[exec] 01:47:10 I/InstrumentationResultParser: test run failed: 'Test run failed to complete. Expected 74 tests, received 70'
[exec] Tests on VirtualBox - 9 failed: Test run failed to complete. Expected 74 tests, received 70
[exec] 01:47:10 I/XmlResultReporter: XML test result file generated at C:\work\workspace\ORCTrunk\orc\tablet\android\ORConnect\app\build\outputs\androidTest-results\connected\TEST-VirtualBox - 9-app-.xml. Total tests 70, passed 32, ignored 38,
However, if you go look at the report or the output xml, the failing tests are simply missing. Both report 70 tests that passes and no failures. The 4 tests that failed with the ClassNotFoundException are simply missing from the reports.
Expected Behavior:
The 4 missing/failed tests should be reported, so that they can be fixed. Otherwise, people will trust the reports that 100% of the tests passed and possibly release a bug.