You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an alternative to keeping the JUnit view open all the time, it would be handy to have notification of test failures show as warnings in the Problems view.
Ideally, the location of the warning (i.e. where you jump to you when you click the warning) should be the top of the stack trace from the test failure. And the description text of the warning should be the exception/error message (e.g. "AssertionError: expected: but was:"). The type of the warning can be something like "Test Failure" for fails and "Test Error" for uncaught throwables.
The text was updated successfully, but these errors were encountered:
You're right. I'm not sure when I'll have time to implement this, so feel free to contribute a patch. Please add a comment to this issue in case you start working on this so we do not implement it twice.
Define a custom problem marker type for test failures.
When a JUnitLoop test session starts, remove all test failure markers
from the workspace.
On each test failure, create a new test failure marker, which appears in
the Problems view and links to the line in the test case where the
failure occurred.
As an alternative to keeping the JUnit view open all the time, it would be handy to have notification of test failures show as warnings in the Problems view.
Ideally, the location of the warning (i.e. where you jump to you when you click the warning) should be the top of the stack trace from the test failure. And the description text of the warning should be the exception/error message (e.g. "AssertionError: expected: but was:"). The type of the warning can be something like "Test Failure" for fails and "Test Error" for uncaught throwables.
The text was updated successfully, but these errors were encountered: