[#ECLIPSE-309] Run As - Local Camel Context - runs unit tests before launching

Fuse IDE

Run As - Local Camel Context - runs unit tests before launching

Created: 13/Jul/11 11:42 AM Updated: 14/Nov/12 01:10 PM

Component/s:

None

Affects Version/s:

None

Fix Version/s:

7.1.0

Environment:

1.1.77

Description

« Hide

Maybe we should consider being able to use the run as without having to run all the unit tests, and those tests must pass before it can start.

Maybe we should have some option to configure if we should run unit tests first or not.

For example I had some old unit test code generated by the wizard, and i was working on a new route, which I could not start using the wizard.

Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.625 sec <<< FAILURE!

Results :

Tests in error:
testCamelRoute(com.foo.CamelContextXmlTest): org.apache.camel.FailedToCreateRouteException: Failed to create route coolRoute: Route[[From[ref:xxx]] -> [Choice[[When[simple{header.gold} -... because of Failed to resolve endpoint: ref://xxx due to: No component found with scheme: ref

Tests run: 1, Failures: 0, Errors: 1, Skipped: 0

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

Lars Heinemann added a comment - 10/Oct/11 12:53 PM

Claus, if we would add such a bypass for the unit test, would you ever fix the broken tests in future? I am not sure if we should add such features as those unit tests should ensure that the application does what it was designed for. Bypassing unit tests is a risk and if used on production systems it is really dangerous.

[ Permlink | « Hide ]

James Strachan added a comment - 10/Oct/11 12:57 PM

I'm with Claus on this.

Maven allows tests to be avoided. There are times when you want to do that. e.g. you know there's an issue, but you want to investigate something; so you wanna run something in IDE and try something out. Also tests can often take a long time (Camel for example takes about an hour!). Sometimes you just wanna run a context and play with it - without the speed/time/failing test impact.

Note maven allows you to build without testing (I do this alot myself when I just wanna build something so I can use it - rather than building it with the tests).

So it makes total sense to allow you to run a camel-context.xml locally without running the tests as an option. Remember running a camel context locally isn't a replacement for the build system or CI system - its just a way to run a camel XML and try it out.