nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

@deployment does it really deploy a process definition ?

heymjo

Hi,

I have this simple test which fails because the process definition is not getting deployed.

@Test
@ContextConfiguration
public class DemoProcessTest extends AbstractTestNGSpringContextTests {

    @Autowired
    private RepositoryService repositoryService;

    @Deployment(resources = {"workflow/demo.bpmn20.xml"})
    public void simpleTest() {
        ProcessDefinition financialReport = repositoryService.createProcessDefinitionQuery()
                .processDefinitionKey("financialReport").latestVersion().singleResult();
        Assert.assertNotNull(financialReport);
    }
}

‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

I can get it to work by putting the deploymentResources attribute of SpringProcessEngineConfiguration, but i thought it would be nicer with the annotation. I also checked act_re_deployment table and indeed it is empty.

Also, @Deployment claims to create *and* delete a deployment around a test method' in the javadoc. When it deletes the deployment will it do a cascade delete ?

Thanks
Jorg

Find more posts tagged with

Comments

frederikherema1

Hi,

All our internal QA used the @Deployment annotation, so it works allright. If you look at the spring-chapter in the userguide, it says you have to use the ActivitiRule, this will scan the test for deployment annotations and do it's magic. Just running a vanilla spring-test won't: http://activiti.org/userguide/index.html#springUnitTest

It cascades, yes. The ActivitiRule javadocs clearly state this:

<br> * <p>You can declare a deployment with the {@link Deployment} annotation.<br> * This base class will make sure that this deployment gets deployed before the<br> * setUp and {@link RepositoryService#deleteDeployment(String, boolean) cascade deleted}<br> * after the tearDown.<br> * </p><br>

heymjo

ah so that's what the ActivitiRule is, i always thought it was a drools thingy.

Anyways i'm using TestNG, this rule stuff looks quite junit specific. Am i out of luck here ?

frederikherema1

Nope, you can always create a custom base-test class in NG that behaves the same on setup/teardown (or whatever it is called inTestNG

<br><br>deploymentId = TestHelper.annotationDeploymentSetUp(processEngine, method.getMethod().getDeclaringClass(), method.getName());<br><br>// … and later…<br><br>TestHelper.annotationDeploymentTearDown(processEngine, deploymentId, method.getMethod().getDeclaringClass(), method.getName());<br>

heymjo

OK with testng it looks like this then:

<br>@Test<br>@ContextConfiguration<br>public class DemoProcessTest extends AbstractTestNGSpringContextTests {<br><br>&nbsp;&nbsp;&nbsp; @Autowired<br>&nbsp;&nbsp;&nbsp; private ProcessEngine processEngine;<br><br>&nbsp;&nbsp;&nbsp; @Autowired<br>&nbsp;&nbsp;&nbsp; private RepositoryService repositoryService;<br><br>&nbsp;&nbsp;&nbsp; private ThreadLocal<String> deploymentId = new ThreadLocal<String>();<br><br>&nbsp;&nbsp;&nbsp; @BeforeMethod<br>&nbsp;&nbsp;&nbsp; public void setup(java.lang.reflect.Method method) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; String id = TestHelper.annotationDeploymentSetUp(processEngine, method.getDeclaringClass(), method.getName());<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; this.deploymentId.set(id);<br>&nbsp;&nbsp;&nbsp; }<br><br>&nbsp;&nbsp;&nbsp; @AfterMethod<br>&nbsp;&nbsp;&nbsp; public void tearDown(java.lang.reflect.Method method) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TestHelper.annotationDeploymentTearDown(processEngine, this.deploymentId.get(), method<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .getDeclaringClass(), method.getName());<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; this.deploymentId.remove();<br>&nbsp;&nbsp;&nbsp; }<br><br>&nbsp;&nbsp;&nbsp; @Deployment(resources = {"workflow/demo.bpmn20.xml"})<br>&nbsp;&nbsp;&nbsp; public void simpleTest() {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ProcessDefinition financialReport = repositoryService.createProcessDefinitionQuery()<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .processDefinitionKey("financialReport").latestVersion().singleResult();<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Assert.assertNotNull(financialReport);<br>&nbsp;&nbsp;&nbsp; }<br>}<br>

it might be possible to use a testlistener as well which i guess are similar to your rules. But then you'll have to see how to initialize the process engine there, i figured it was nicer to just reuse the instance as initialized by the test. I put the deployment id as a threadlocal to allow testng parallel test execution (untested). AFAICT the ActivitiRule does not allow this but can ofcourse be easily modified.

HTH
Jorg

frederikherema1

Thanks for sharing