[
https://issues.apache.org/jira/browse/OOZIE-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445352#comment-13445352
]
Alejandro Abdelnur commented on OOZIE-975:
------------------------------------------
I'm a bit puzzled on why they would conflict? Furthermore, I think it is good
we test things with most/all of them loaded as that would identify runtime
issues. If you need a special behavior in any of those services, you can always
override them in the setUp() method of the testcase, by adding an overriding
impl via setSystemProperty() to 'oozie.services.ext', or by using
Services().get().setService(). What is the exact issue you are seeing here.
> Test cases should not load all the services classes
> ---------------------------------------------------
>
> Key: OOZIE-975
> URL: https://issues.apache.org/jira/browse/OOZIE-975
> Project: Oozie
> Issue Type: Bug
> Reporter: Virag Kothari
> Assignee: Virag Kothari
> Attachments: kill-output.txt
>
>
> Some services classes loaded as part of services.init() interfere with the
> actual test case causing them to break.
> TestPauseTransitSErvice, TestPurgeService, TestActionCheckerService keep
> failing intermittently.
> Related pre-commit build links:
> https://builds.apache.org/job/oozie-trunk-precommit-build/58/testReport/junit/org.apache.oozie.service/TestPauseTransitService/testUnpauseBundleAndCoordinator/
> https://builds.apache.org/job/oozie-trunk-precommit-build/55/testReport/junit/org.apache.oozie.service/TestActionCheckerService/testActionCheckerServiceCoord/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
