rclabo commented on issue #406: URL: https://github.com/apache/lucenenet/issues/406#issuecomment-771872803
>Sounds good in theory, but in Lucene.NET we are limited to running tests serially due to shared static members in the test framework. I kinda thought that might be the case. I see no pressing reason to switch from serially running the tests. That keeps our lives more sane. >All existing test project targets can use the latest version of NUnit, 3.17. >"Copy Details" seems to have some finite limit. If the amount of text exceeds the limit, it is truncated and may not be very useful. Unfortunately, the Lucene tests were designed with an infinite amount of space to log into. >I don't find the logging here particularly useful either. However, it is not just meant for the Lucene.NET team, it is meant for anyone that consumes the test framework - therefore, it should be set up in a reasonable way to make debugging easy for those who depend on it. If we go to with NUnit 3.17 then the full output of `Console.WriteLine` will go to the output window in VS, for all tests except the .NET Standard 2.0 tests running NUnit 3.10.1 (for Xamarin compatibility). So that kinda solves the truncation problem and sounds like a good plan for how to move forward. Since you were planning on regressing the .NET Standard 2.0 tests to NUnit 3.10 anyway, do you want to be the one to upgrade the other compilation targets to use NUnit 3.17 at the same time? I can do it, but it seems like a good fit for you to do it with the .NET Standard 2.0 XUnit change. >although I wasn't planning on releasing the test runner I created along with Lucene.NET, it is just to verify compatibility with mobile platforms. Is it available elsewhere where I could take a look at it just to better understand what such a test runner looks like? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
