Hello, We have an error participant that takes care of a host of things in the event that a runtime error occurs... I think the type of error I want to catch at this stage in the development process is that we have incorrectly defined the workflow logic in a new or modified workflow, which results in an unexpected workitem getting generated. In this case, our test suite is calling dashboard.wait_for(expected_workitem), so it just hangs, waiting ever so patiently for a workitem to appear that will never appear due to our (usually my) logic error.
I think the timeout is still the best approach for the moment, I just haven't had time to play with it yet. We know from trial and error about how long it takes for workitems to get generated during the testing process, so I can conceivably just set the timeout at a second or two past that, and throw an exception. This would at least have the benefit of allowing the testing suite to continue with a red test and an error noisy enough that we can figure out how to correct it. Thanks for your help!! - jrob -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en
