Skip to content

One of the things that has been bugging me for a couple of years is that for my FileNet ECM projects the testing of my workflows could not be scripted. This is mainly to do with the stateful nature of the workflows and mocking the connection is not an option.

License

boudie65/IBM-FileNet-WorkflowTestFramework

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

IBM-FileNet-WorkflowTestFramework

A TestNG Framework to be able to Unit Test IBM FileNet workflows

Usage

To test if the workflow object is at a specific step, use the assertAtStep. Verify the settability of a parameter with asserParameterIsReadWriteable or assertParameterIsNotReadable

For instance

public void testVerifyAtStepEnterValues() {
    String atStepName = "Enter case value";
    VWWorkObject wob = ops.getWorkObject();

    assertAtStep(wob, atStepName);
    assertParameterIsReadWriteable(wob, "CaseValue");
    assertParameterIsReadWriteable(wob, "CaseName");
    assertParameterIsNotReadable(wob, "IsApproved");
}

Additional resources

http://www.patrickvanderhorst.info/blogs/filenet-workflow-test-framework-(part-1-of-3).html http://www.patrickvanderhorst.info/blogs/filenet-workflow-test-framework-(part-2-of-3).html http://www.patrickvanderhorst.info/blogs/filenet-workflow-test-framework-(part-3-of-3).html

About

One of the things that has been bugging me for a couple of years is that for my FileNet ECM projects the testing of my workflows could not be scripted. This is mainly to do with the stateful nature of the workflows and mocking the connection is not an option.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages