I will try to work with them to help them get coverage for this case. This feels very much like a bug or a regression for which JetBrains doesn’t have test coverage. In 9.2, the test explorer shows all of the tests correctly, so R# is clearly able to interpret the hierarchy and attributes (noted above) as I’ve intended them to be interpreted. As I mentioned, test-running for the exact same solution with 8.2.3 is error-free and a pleasure to use. While it’s possible that there’s something I’m doing wrong, or there’s something in my installation that’s strange, I don’t think that’s the problem.
There’s a beta version for 9.1 that caused noticeable lag, so I’m still waiting for a more unobtrusive version for 9.2 (or any version at all). In 9.2, it’s not only inconvenient, but I’m worried that my tests are not being executed with the expected configuration.Īlso, I really missed the StyleCop plugin for 9.2. However, if I elect to run them all by running the parent node, R# once again marks everything as inconclusive.Īs I mentioned, 8.2.3 handles this correctly and I feel R# 9.2 isn’t far off-the unit-test explorer does, after all, show the correct tests and counts.
If I select multiple test fixtures in the explorer and add them, they also show up as expandable nodes, with the correct test counts, and can be executed individually (per fixture). If I select a specific, concrete fixture and add or run those tests, R# loads and executes the runner correctly. Running an individual test-fixture node does not magically cause the tests to load or appear and also shows inconclusive (after a while it seems the fixture setup executes as expected but the results are not displayed). If I select a node for all tests for ProviderB and ProtocolA (696 tests in 36 fixtures), R# loads 36 non-expandable nodes into the runner and, after a bit of a wait, marks them all as inconclusive. The test explorer shows all of the tests correctly, with the test counts correct. The test runner in 9.2 is not happy with this at all. (TMixin = ProtocolBProviderB TestFixtureAttribute, CategoryAttributes) (TMixin = ProtocolAProviderB TestFixtureAttribute, CategoryAttributes) (TMixin = ProtocolBProviderA TestFixtureAttribute, CategoryAttributes) (TMixin = ProtocolAProviderA TestFixtureAttribute, CategoryAttributes) (defines tests with NUnit TestAttributes) (7 of these, one with an NUnit CategoryAttribute)
The top layers provide scenario-specific input via a generic type parameter. There are quite a few base classes providing base functionality. These tests are not straight-up, standard tests, but R# 8.2.3 handled them without any issues whatsoever. As with 9.0 and 9.1, I am unable to productively use the 9.2 Test Runner with many of my NUnit tests.
0 kommentar(er)
