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
I have noticed that when running unit tests, the button for reruning failed tests in Test Results never gets enabled.
How to reproduce
Create Java with Maven project
Add some unit tests that fail
Run tests and check the button - should be enabled but it's not.
Did this work correctly in an earlier version?
No / Don't know
Operating System
Manjaro Linux
JDK
OpenJDK 11
Apache NetBeans packaging
Apache NetBeans binary zip
Anything else
I checked the source code and the problem seems to be in the condition rerunFailedButton.setEnabled(displayHandler.sessionFinished && rerunHandler.enabled(RerunType.CUSTOM) && !treePanel.getFailedTests().isEmpty());
in netbeans/ide/gsf.testrunner.ui/src/org/netbeans/modules/gsf/testrunner/ui/StatisticsPanel.java
RerunType.CUSTOM doesn't seem to be used anywhere thus the condition is always false. Using RerunType.ALL fixes the issue, but I am not sure if it has any side-effects, I haven't found any yet.
Are you willing to submit a pull request?
Yes
The text was updated successfully, but these errors were encountered:
Apache NetBeans version
Apache NetBeans 18
What happened
I have noticed that when running unit tests, the button for reruning failed tests in Test Results never gets enabled.
How to reproduce
Did this work correctly in an earlier version?
No / Don't know
Operating System
Manjaro Linux
JDK
OpenJDK 11
Apache NetBeans packaging
Apache NetBeans binary zip
Anything else
I checked the source code and the problem seems to be in the condition
rerunFailedButton.setEnabled(displayHandler.sessionFinished && rerunHandler.enabled(RerunType.CUSTOM) && !treePanel.getFailedTests().isEmpty());
in netbeans/ide/gsf.testrunner.ui/src/org/netbeans/modules/gsf/testrunner/ui/StatisticsPanel.java
RerunType.CUSTOM doesn't seem to be used anywhere thus the condition is always false. Using
RerunType.ALL
fixes the issue, but I am not sure if it has any side-effects, I haven't found any yet.Are you willing to submit a pull request?
Yes
The text was updated successfully, but these errors were encountered: