-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
App completes successfully but XHarness tool fails #91
Comments
I was able to resolve the first problem with the XML header: #93 |
The reason we are generating NUnit results always is here: xharness/src/Microsoft.DotNet.XHarness.Tests.Runners/iOSApplicationEntryPoint.cs Lines 38 to 48 in bc6dca4
@mandel-macaque currently the TestRunner can never output xUnit results ^^ So the |
The skipped test problem might be an issue with the wrong XML result jargon |
The reason for not recognizing that tests finished successfully is here: xharness/src/Microsoft.DotNet.XHarness.iOS.Shared/XmlResultParser.cs Lines 54 to 58 in bc6dca4
But I am a bit confused. The above corresponds with what I found here: The XML returned from Egor's app should also be NUnit v3, but somehow it is v2 and we only succeed if we try to parse it as NUnit v3... This is weird |
Oops, got auto-closed |
As mentioned here: #91 (comment), we include some garbage in the results XML
The following PR should fix a number of the issues: #102
|
So I guess after #102 we only need to find out how stuff gets to |
Egor has built me an app from these tests:
The app runs fine, it terminates but we fail to parse the results:
The header makes it an invalid XML:
Also number of tests ran doesn't correlate with the code:
The skipped test is mentioned in the logs though:
Problems to be solved
nunit-test-ios-simulator-64-20200427_010223.xml
- there's no nunit involved [iOS] Ensure that we do generate xml when we call the CLI. #102The text was updated successfully, but these errors were encountered: