Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
I see you support test-framework, I assume this means invoking a test directly without a main ??
Any plans to support hspec ?
No, there is still a main and an executable being generated with test-framework. The support for it in EclipseFP means that EclipseFP automatically passes options to that executable, for example to generate a XML file that is used as the input of the JUnit test result view.
I didn't know about hspec before, so no, there was no plans for it (-:. I suppose you can either make an entry in the "Backlog" tracker on sourceforge or on my EclipseFP github repo with the enhancement request so we keep a trace of it.
How exactly do I use EclipseFP with test-framework? I created a sample test file, added an executable for it, and I can successfully run it manually. How do I create a run configuration for it? I don't see an entry in "Run as" and manually creating a run configuration with type "Test-framework test" doesn't get me anywhere. It always says "Working directory does not exist or is invalid." when I use the project root or the specific folder where the test resides.
You open the cabal file editor on the cabal file of your project, and you add a test suite section, pointing to your executable test. then you can choose to run the test section, the run config will be created for you.
Ah, didn't see this. I created a test suite with "using test framework" and chose the test main. What should I do now? I don't see a new run config or any way to let it create one.
In project explore expand the cabal file you'll see the test stanza, you can right click run. I think running the project will prompt you for which stanza to run.
Tricky! I see my test suite and can right click "run", but then I have to select a launch configuration but the list is empty.
Don't know, works fine usually. Have you built your project? No errors? Do you see the test executable under the .dist-buildwrapper/dist/build/testsuitename ?
I got it working now. The problem was that there was a build error in modules belonging to a different executable. As the test code was completely independent I thought that this would be no problem.
Somewhere I read that I would now have JUnit integration, but it's still just the console. Is this already implemented?
Also, how would I use the test type "module"?