topic Re: Completing user task in unit testing, async behavior in Alfresco Archive

Completing user task in unit testing, async behavior

sor1 — Tue, 06 Nov 2012 21:07:39 GMT

I have some unit tests in the same test class checking that a user task appears and completing it. It was working perfectly but now I have set the first service task (before the user task) of my process to async=”true”.So, I had to change the code of the tests to wait that the user task appears afte

Re: Completing user task in unit testing, async behavior

sor1 — Wed, 07 Nov 2012 08:56:00 GMT

If I replace the runtimeService used to start the process by:
ProcessEngines.getDefaultProcessEngine().getRuntimeService();
in stead of the runtimeService proposed by the ActivitiTestCase my tests work.

Do you understand why?

Re: Completing user task in unit testing, async behavior

frederikherema1 — Thu, 08 Nov 2012 09:49:10 GMT

Not really getting the initial problem. Are you setting the jobExecutorActivate to FALSE? This makes sense the test fails, the async jobs will never be executed.

If you use ProcessEngines.getDefaultProcessEngine().getRuntimeService(), ANOTHER process-engine will be created, using activiti.cfg.xml on the class path (eg. src/main/resouces). If this contains an ACTIVE job-executor, it makes sense the tests run…

Re: Completing user task in unit testing, async behavior

sor1 — Thu, 08 Nov 2012 10:19:21 GMT

Thanks a lot,
I want to use jobExecutorActivate to TRUE (I have tried to use jobExecutorActivate to FALSE to see if it solves my problem, but now just forget this test)

To start the process, if I use runtimeService (of ActivitiTestCase) or ProcessEngines.getDefaultProcessEngine().getRuntimeService() in both cases the activiti.cfg.xml file used is in src/test/resources.
So in both case, the property jobExecutorActivate" value="true" is used.
So the reason why it work with ProcessEngines.getDefaultProcessEngine().getRuntimeService() is still unknown.