Commit ID 38004df8f9f0c37dd9af235caf1ea6a489060b49
|Contributor:||Gunnar Wagenknecht||Files Modified:||35|
|Date:||07-October-2012 at 06:30||Lines Added:||1177|
|Repository:||git://git.eclipse.org/gitroot/gyrex/gyrex-platform.git master||Lines Removed:||1006|
|Commit Comment:||replace custom test application with JUnit 4 rule/resource
This commit removes the custom Gyrex test application. Thus, instead of
patching PDE and Tycho to launch a custom app a JUnit 4 standard
mechanism has been adopted. A new rule is now available, which can be
used in suites and tests to require the start of a Gyrex server. Rules
can be nested.
However, the drawback of this approach is that clients must be carful
what to rely on in their bundle activators. For example, test bundles
must be aware that Gyrex may not be running when their bundle activator
is started. Consequently, a test bundle my trigger bundle activation for
another bundle. Such a bundle must also be prepared that a server
environment has not been initialized yet.
Signed-off-by: Gunnar Wagenknecht <gun...@wagenknecht.org>
|File||Language||Code Added||Code Removed||Comments Added||Comment Removed||Blanks Added||Blanks Removed|
|...clipse.gyrex.boot.tests/build.properties||No source code was detected in this file.|
|...tests/.settings/Gyrex Cloud Tests.launch||XML||231||0||0||0||0||0|
|...Gyrex Cloud Tests (within server).launch||XML||0||230||0||0||0||0|
Copyright © 2013 Black Duck Software, Inc. and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a Creative Commons Attribution 3.0 Unported License . Ohloh ® and the Ohloh logo are trademarks of Black Duck Software, Inc. in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.