We can't agree more! Ideally the user would have the liberty to configure MoreUnit to run any test configuration: Code Coverage, With Debugging, Eclipse Plugin Test, etc. Unfortunately Eclipse's test/program run system is quite complex and it would we be really hard to implement. Running simple JUnit or TestNG Tests has already caused us some headaches :-)
That said, we will keep your ticket open: maybe we will finally find the right way to implement it!
Regards,
Nicolas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If I could get coverage to run, I'd like to have a view which is automatically linked to the current CTRL-J target content.
If I'm in the code, it shows the current test.
If I'm in the test, it shows the code for the method along with most recent coverage.
When I CTRL-R or CTRL-SHIFT-ALT-R, the coverage automatically updates, either in the editor or in the view depending on the scenario.
The utility here is that it provides complete visibility into coverage without having to toggle between views, or do anything really. I can use MoreUnit to help me test as I normal do. I see both test and code together always, at the low cost of some screen real estate. Finally, I get immediate coverage feedback, at whatever scope I choose (CTRL-R or CTRL-SHIFT-ALT-R).
Some may find such a linked view useful even without coverage.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Eduardo,
We can't agree more! Ideally the user would have the liberty to configure MoreUnit to run any test configuration: Code Coverage, With Debugging, Eclipse Plugin Test, etc. Unfortunately Eclipse's test/program run system is quite complex and it would we be really hard to implement. Running simple JUnit or TestNG Tests has already caused us some headaches :-)
That said, we will keep your ticket open: maybe we will finally find the right way to implement it!
Regards,
Nicolas
Seeing the coverage provided by a ctrl-alt-shift-R usage would be insanely productive.
If I could get coverage to run, I'd like to have a view which is automatically linked to the current CTRL-J target content.
If I'm in the code, it shows the current test.
If I'm in the test, it shows the code for the method along with most recent coverage.
When I CTRL-R or CTRL-SHIFT-ALT-R, the coverage automatically updates, either in the editor or in the view depending on the scenario.
The utility here is that it provides complete visibility into coverage without having to toggle between views, or do anything really. I can use MoreUnit to help me test as I normal do. I see both test and code together always, at the low cost of some screen real estate. Finally, I get immediate coverage feedback, at whatever scope I choose (CTRL-R or CTRL-SHIFT-ALT-R).
Some may find such a linked view useful even without coverage.