If I click "Run Last Launched" to reexecute the previously launched JUnit tests after doing some changes in the source code, JUnit will start even through compilation errors are found in the source code just modified. This can cause confusion because the focus is immediately set on the "JUnit" tab, and hence errors listed in the "Problems" tab are hidden. Yep, there is a little red "x" appearing on the Problems tab index, but it can be difficult to spot when the JUnit tab activates itself.
When this condition arises, it would be nice if Eclipse could pop up a modal window saying "The are compilation errors; do you want to launch JUnit anyway?". This behavior is generally found in other IDEs.
When this condition arises, it would be nice if Eclipse could pop up a modal window saying "The are compilation errors; do you want to launch JUnit anyway?". This behavior is generally found in other IDEs.
Leave a comment
I thought that is already implemented because Eclipse can prompt to run a main method if there are errors in the project. But it doesn't seem to work for JUnit tests. Technically this is an issue with Eclipse and not Scala IDE but we could hack a check into our own Scala JUnit launcher but then it would only work if this one is used to run JUnit tests. Also, it is quite unlikely someone will work on that because it is quite a low priority issue.
No file chosen
You have an empty file field. Please select or remove it.
Name | Size |
---|