-
Notifications
You must be signed in to change notification settings - Fork 9
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
Improve TestCaseNameParser #28
Comments
Hi, examples would be good. |
Here are some examples. I simplified some info to focus on the test case examples at hand, but please let me know if you'd need more information: Example Test 1
Example Test 1 - Results in TestResults.xml
Example Test 2
Example Test 2 - Results in TestResult.xml
Example Test 3
Example Test 3 - Results in TestResults.xml
Example Test 4
Example Test 4 - Results in TestResults.xml
Example 5Then there are these ones that work if I replace
Example 5 - Results in TestResults.xml
|
Hi, So example 3 was just fixed. Example 2 looks like a fixable issue with the parser. Everything else seems to be facing the same problem. The parser is expecting the string it is given to parse would look like valid c#. Note that we get a single string representation of the test name from For Example 5, its the same kind of issue, but I'm not sure this is something we can directly support. If the default format is overridden and it isn't something we can parse, then there isn't much we can do. Depending on what else we come up with, we could always offer an option to do something different on a parsing failure. Presumably not adding the UnknownNamespace and UnknownType text. For my notes: |
Co-Authored-By: Rebekah Cha <[email protected]>
Updated testlogger dependency. See spekt/testlogger#28
@codito Hi. I think all three loggers are ready to be released with these updates. Just wanted to see if we can do that or if you were waiting on me to do something. |
@Siphonophora sorry for the delay, work is a bit hectic at this time. I hope to cut a release in a week or so. |
@Siphonophora we have pushed junit testlogger to nuget: https://www.nuget.org/packages/JunitXml.TestLogger/3.0.114 |
just wondering if there's any progress for pushing out an update for the nunit test logger? |
@becha2 I didn't realize that spekt/nunit.testlogger#93 was waiting on me. As soon as it gets merged there will be a pre-release version in myget. |
https://www.nuget.org/packages/NunitXml.TestLogger/3.0.127 is also released. |
awesome! thank you |
Hello! We are running into a lot of "Unable to parse the test name" errors in our test scripts for certain kinds of parametrized tests when the inputs are valid. This adds a ton of noise in our logs, making finding actual errors difficult for our developers. Could the parser be improved? Looking at the remarks on the class, it seems there can be some big wins. I can provide some examples if needed. We run these tests in both NET Framework 4.7.2 and NET 5.0 and the errors occur in both cases.
The text was updated successfully, but these errors were encountered: