Problem: If a test fails, it's kinda a pain because you need to go into the Actions tab, scroll through the history, etc until you finally see the failed test. Then you need to see what line of the test, look at debug logs to see if that helps, etc. You may be able to find the issue from just reading the code but more then likely you need to run the tests on your local dev environment.
This action is cool. I am thinking of making junit specific tools and as long as we can make sure all tests that we run (unit, integration, ui, etc) they generate junit results then we can use all these tools for the results.
Problem: If a test fails, it's kinda a pain because you need to go into the Actions tab, scroll through the history, etc until you finally see the failed test. Then you need to see what line of the test, look at debug logs to see if that helps, etc. You may be able to find the issue from just reading the code but more then likely you need to run the tests on your local dev environment.
This action is cool. I am thinking of making junit specific tools and as long as we can make sure all tests that we run (unit, integration, ui, etc) they generate junit results then we can use all these tools for the results.