"maxwarnings" argument is not properly passed when starting tests from Test View.

If you use the -maxwarnings 0 parameter, there should be no limit for debug messeges in the output. This is the case if you start the test application in the traditional way. Unfortunately the above parameter does not seem to work if you launch the test from the Test View. In the Tests Explorer it is shown that you should use just the above argument - it seems to be ignored.

It doesn't seem to be anything critical, but it makes analysis more difficult if some test is not working and you add additional logs for better diagnosis and those logs are not visible. Test View is great solution because you can run only selected set of tests, but potentially missing logs make it very difficult to use in my case.