Teodor Nacu

I gave up using composer. I use Android Test Orchestrator for robustness and it will crash only the affected test, but not the entire tests class and the xml is...

@abjerstedt I am not using gradle to build with the Android Test Orchestrator. I just deploy the orchestrator apks to the emulator and then run the tests with the orchestrator....

I 've written a tool that parses the TestSummaries plist file from Logs/Test folder and generates the JUnit report xml file: (https://github.com/nacuteodor/ProcessTestSummaries) You shouldn't have this problem with that tool....

@silverhammermba Have you tried to use https://github.com/nacuteodor/ProcessTestSummaries tool for creating the tests results report? That doesn't have this issue.

@ogantopkaya I 've written a tool that parse the TestSummaries plist file from Logs/Test folder and generates the JUnit report xml file: (https://github.com/nacuteodor/ProcessTestSummaries) The test results use the target name...

Hey @jpdutoit , I 've written a tool that parses the TestSummaries plist file from Logs/Test folder and generates the JUnit report xml file: (https://github.com/nacuteodor/ProcessTestSummaries) You shouldn't have this problem...

@rkubik Have you tried https://github.com/nacuteodor/ProcessTestSummaries tool to generate the JUnit report? I am not sure if the mentioned error is related with generating the JUnit report.

@Apocryphon I 've written a tool that parses the TestSummaries plist file from Logs/Test folder and generates the JUnit report xml file: (https://github.com/nacuteodor/ProcessTestSummaries) Also, an output log of the UI...

Welcome @jameseisenhauer! I am glad that helps you.