can't always run spec2 (SpecificationWithJUnit) or junit testcases
Can't run testcases, neither Java (junit) nor Scala (spec2) on scala projects. I've to modify the
testcase, save it, sometimes it runs sometimes it doesn't, maybe then
clean and rebuild the project, sometime it works and sometime it
doesn't. I did have this issue in the past but it was rare, now this
problem is occuring most of the time.
Eclipse reports "No tests found with test runner 'JUnit 4'"
I had this issue even with RC01 and older versions of the scala plugin. But now I've noticed this to occur in java projects that I've added the scala nature.
It might be cause my projects are maven projects. I am using the m2e plugin (please see attached for a full plugin list)
As I work around, if I close and reopen the project and before RC01, it then seemed to be able to run the testcase. From RC01 and on it doesn't help. I need to open the testcase, do a no-op edit, save it and then it runs the testcase (most of the time).
testcase, save it, sometimes it runs sometimes it doesn't, maybe then
clean and rebuild the project, sometime it works and sometime it
doesn't. I did have this issue in the past but it was rare, now this
problem is occuring most of the time.
Eclipse reports "No tests found with test runner 'JUnit 4'"
I had this issue even with RC01 and older versions of the scala plugin. But now I've noticed this to occur in java projects that I've added the scala nature.
It might be cause my projects are maven projects. I am using the m2e plugin (please see attached for a full plugin list)
As I work around, if I close and reopen the project and before RC01, it then seemed to be able to run the testcase. From RC01 and on it doesn't help. I need to open the testcase, do a no-op edit, save it and then it runs the testcase (most of the time).
Leave a comment
on 2011-11-30 00:33 *
By Mirco Dotta
Assigned to set to Mirco Dotta
Status changed from New to Need Info
on 2011-11-30 01:54 *
By kostas.kougios
I've uninstalled springIDE and the problem persists. This problem occured in all scala ide versions, since I started using it. Both RC1 and RC2 in an installation that doesn't include springIDE, have the issue.
It might have something to do with m2e, as all my projects are maven projects and the test classes are under a different directory.
Running a test with Helios will be hard at the moment as my workspace is on Indigo. But when is ScalaIDE 2.1 going to be ready?
It might have something to do with m2e, as all my projects are maven projects and the test classes are under a different directory.
Running a test with Helios will be hard at the moment as my workspace is on Indigo. But when is ScalaIDE 2.1 going to be ready?
on 2011-11-30 11:16 *
By Mirco Dotta
If you are using Indigo, then JUnit test discovery does not work (#1000782). Usually, if you open the test file you want to run, and then try to run it (while it is still open in the editor), then it should work. As I said, this is a know problem with Indigo, which we do not fully support yet. Development for the ScalaIDE 2.1 is already ongoing (there is a nightly update site for it: http://download.scala-ide.org/nightly-update-master-2.9.1), but we haven't yet start working on Indigo support. It will happen soon enough, just keep an eye on the master branch (https://github.com/scala-ide/scala-ide).
on 2011-11-30 11:17 *
By Mirco Dotta
If you agree, I'd file this as a duplicate of #1000782. What do you think?
on 2011-12-01 00:09 *
By kostas.kougios
yes,sure (I can't seem to be able to do that myself)
No problem, I can do it myself. Thanks for the feedback. I'm invalidating the ticket then, since #1000782 provide a simple way to reproduce this.
on 2011-12-16 11:52 *
By Mirco Dotta
Kostas, why did you add the above image? Isn't #1000782 the same issue you are experiencing?
on 2011-12-16 12:48 *
By kostas.kougios
hmm, definately I didn't add this image today on 8:45!!! I did attach it when I opened the bug, days ago :
"It might be cause my projects are maven projects. I am using the m2e plugin (please see attached for a full plugin list)"
I don't know why it reappeared now.
"It might be cause my projects are maven projects. I am using the m2e plugin (please see attached for a full plugin list)"
I don't know why it reappeared now.
on 2011-12-16 13:37 *
By Mirco Dotta
LOL. Alright, no issue. I was just wondering... :)