I have no test output when tests are run by the continuous test runner, but I still have test output in when running tests from the "regular" test runner window.
Same here... not getting any output whatsoever, whereas the previous version used to show all of our log4net output, which was very useful. Hope this gets fixed soon :s
Apologies all. This is a showstopper that managed to slip into the final release. We're releasing a bug fix very soon, hopefully next week. In the meantime, you can work around the issue by not clicking parent nodes in the tree - if you click only tests, the output will update correctly, but if you select a parent, the output can get stuck. If it does get stuck, right click on the tests you want to run again and select "create new session", which will create a new tab in the test sessions window, and allow you to run the tests again. Not ideal, but you can at least keep working. Once again, apologies.
I have no test output when tests are run by the continuous test runner, but I still have test output in when running tests from the "regular" test runner
window.
Same here... not getting any output whatsoever, whereas the previous version used to show all of our log4net output, which was very useful. Hope this gets fixed soon :s
Apologies all. This is a showstopper that managed to slip into the final release. We're releasing a bug fix very soon, hopefully next week. In the meantime, you can work around the issue by not clicking parent nodes in the tree - if you click only tests, the output will update correctly, but if you select a parent, the output can get stuck. If it does get stuck, right click on the tests you want to run again and select "create new session", which will create a new tab in the test sessions window, and allow you to run the tests again. Not ideal, but you can at least keep working. Once again, apologies.
Here's the ticket to track: https://youtrack.jetbrains.com/issue/RSRP-450381
can confirm that the workaround works