You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Robert Kanter (JIRA)" <ji...@apache.org> on 2015/02/23 19:12:17 UTC

[jira] [Commented] (OOZIE-2148) Oozie Unit testing framework

    [ https://issues.apache.org/jira/browse/OOZIE-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333607#comment-14333607 ] 

Robert Kanter commented on OOZIE-2148:
--------------------------------------

Thanks for taking this up.  Having an easy to use testing framework like this will be very helpful for users trying to figure out complicated coordinators.  

Are you planning on fixing up LocalOozie and/or MiniOozie?  
Or are you going to start from scratch?  (in which case, I think we would deprecate LocalOozie and MiniOozie).

> Oozie Unit testing framework
> ----------------------------
>
>                 Key: OOZIE-2148
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2148
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Purshotam Shah
>            Assignee: Purshotam Shah
>
> There is no proper document on how and to use Oozielocal/OozieMini for testing.	
> We need to validate how well it for works for bundle and coords.
> We need to provide an easy way to submit jobs ( wf, coord, bundle) and and an efficient  way to assert.
> We also need to provide way to test workflow with sharelib, hcat ( with cred), hbase etc... 
> We also need to create testing documentation, so that user can unit test there WF/coord/bundle  before deploying to prod.
> Few of the usecase which our user will be using ( will add some more).
> 1.Submit coordinator.xml with X properties.
>   assert that workflows are submitted at frequency X.
>   first one starting at time Y, with variables A,B,C set to values D,E,F in the workflow.
> 2. Submit bundle, show that the coordinators start at expected times.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)