typecasting number to char and Assert make the code not run. #996
Replies: 4 comments 12 replies
-
This is part of the FQN issues. So yes, it is a bug, but there are multiple similar to this one, see https://github.com/nunit/nunit3-vs-adapter/issues?q=is%3Aopen+is%3Aissue+label%3Ais%3AFQNIssue @CharliePoole @supawichza40 says it works with the console, but from the xml dump file I see that there is no events coming from the engine for the test. It says it finds one test, so why is this working with the console and not the adapter/engine ? I have enclosed the execution dump file. |
Beta Was this translation helpful? Give feedback.
-
A quick note for clarification... the engine generates start-run and test-run events. All other events are merely passed through from the framework. So if there is no test-suite or test-case event, that means the framework never ran the tests. |
Beta Was this translation helpful? Give feedback.
-
@OsirisTerje I see that on line 17 of the dump. But on line 43 I see " (At Execution) Issue996.Tests.Test1("1",'\u0001')" That's what I was asking about |
Beta Was this translation helpful? Give feedback.
-
IMO adding the owners team is a mistake. It doesn't give us the authority to do anything we can't already do as owners but it misleads people as to our role in your project. I notice yours is not the only project that has done this, however. |
Beta Was this translation helpful? Give feedback.
-
NUnit frame work use 3.13.3
NUnit3TestAdapter iinstalled 4.2.1
Hi, guys, I know that this is not a high priority, but I think it is a bug and must be reported, so I tried to compare a type casting of the number to char, and compare it to another string, but as a result, make that test not runnable.
and since you can run the same test on the console runner, they said that it must be a problem with the adapter, could you inform me if this is a bug, or is there a configuration you need to do.
Beta Was this translation helpful? Give feedback.
All reactions