topic Re: Unit test does not load test data in Alfresco Archive

Unit test does not load test data

kaihuener — Sat, 14 Dec 2013 23:18:56 GMT

Hey all,I want to write a simple unit test in a standard maven directory structure. An activiti.cfg.xml file is located in src/main/resources with all relevant configuration (database, ldap, mail, etc). For the unit test, I want to replace several configuration, e.g. H2 in-memory as database.I also

Re: Unit test does not load test data

frederikherema1 — Mon, 16 Dec 2013 07:40:53 GMT

1) That what you want, right?
2) org.activiti.spring.ProcessEngineFactoryBean is just a factory-bean. If you know your way around spring, it will create an instance of a bean, when the "getInstance" is called. So it's a factory for other types of beens, and in this case, it creates ProcessEngine(Impl) beans. This is exactly what it's designed to do.
3) Spring will only call the init-method if the spring-context is started and the bean is created. The way the "default" activiti-configuration works is that it does NOT boot an application-context. Rather, it just uses the bean-definitions in the activiti.cfg.xml file to extract the processEngine itself. If you want to use activiti in a spring-context, you should boot up the engine USING the application-context and depend on that bean instance, instead of depending on the ProcessEngines.getDefault().

Fortunatly, we have base spring-tests for that as well, so you can point to a valid spring-context file (which you already have). An example of this can be found in the org.activiti.spring.test.components.ProcessStartingBeanPostProcessorTest class:


/**
 * @author Josh Long
 */
@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration("classpath:smileysurprised:rg/activiti/spring/test/components/ProcessStartingBeanPostProcessorTest-context.xml")
public class ProcessStartingBeanPostProcessorTest {

 private Logger log = LoggerFactory.getLogger(getClass());

 @Autowired 
 private ProcessEngine processEngine;
 
 @Autowired 
 private ProcessInitiatingPojo processInitiatingPojo;
 
 @Autowired
 private RepositoryService repositoryService;
 
 @Before
 public void before() {
   repositoryService.createDeployment()
     .addClasspathResource("org/activiti/spring/test/autodeployment/autodeploy.b.bpmn20.xml")
     .addClasspathResource("org/activiti/spring/test/components/waiter.bpmn20.xml")
     .deploy();
 }

You can just used the injected process-engine, instead of depending on the base-class to do the initialisation.

Re: Unit test does not load test data

kaihuener — Thu, 19 Dec 2013 16:15:23 GMT

Frederik – again you, thank you so much! Will have to send you some christmas presents for all this great support, right?
For those who have a similar question: I change the test as follows:
<code>import static org.junit.Assert.assertTrue;
import org.activiti.engine.ProcessEngine;
import org.activiti.engine.test.ActivitiRule;
import org.junit.Rule;
import org.junit.Test;
import org.junit.runner.RunWith;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.test.context.ContextConfiguration;
import org.springframework.test.context.junit4.SpringJUnit4ClassRunner;
import cdq.cdl.bpr.shared.Constants;

@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration("classpath:activiti.cfg.xml")
public class TestBasic {

@Rule
public ActivitiRule activitiRule = new ActivitiRule();

@Autowired
private ProcessEngine processEngine;

@Test
public void testLogin() {

boolean check = activitiRule.getIdentityService().checkPassword("foo"; "bar");
assertTrue(check);
}
}</code>
I also had to explicitly add spring-context dependency with "3.2.5" version to the project's POM file because (in my case), only an older version was resolved by maven. But this may be due to my specific settings – here just as a hint.

So far – thank you and best regards,
Kai