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.

Junit shows me old result

tomi87

Hello,
I don't know why my Junit shows me the whole tome the same error message. I removed or changed the most stuff from my test (with the mistake), but Junit shows me still the old error message.
I'm using in my code:

   
…
      TaskService taskService = activitiRule.getTaskService();
      Task task = taskService.createTaskQuery().singleResult();
      FormService formService = activitiRule.getFormService();
…
List<HistoricDetail> historyVariables = activitiRule.getHistoryService()
                   .createHistoricDetailQuery()
                   .variableUpdates()
                   .orderByVariableName()
                   .asc()
                   .list();
         
            assertNotNull(historyVariables);

            assertEquals(2, historyVariables.size());
            HistoricVariableUpdate abc= ((HistoricVariableUpdate) historyVariables.get(1));
…
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Find more posts tagged with

Comments

frederikherema1

This is not something activiti-specific, but JUnit/Eclipse related… Try google

tomi87

I had this kind of stuff before.
But I don't know how I fixed this. But it was activiti specific.

This is my code:

<br>public class CreateIdNumberTest {<br><br> @Rule<br> public ActivitiRule activitiRule = new ActivitiRule("activiti.cfg-mem-fullhistory.xml");<br><br> @Test<br> // deploys process with form properties<br> @Deployment(resources = { "part2Arrival/createIdNumber.bpmn20.xml" })<br> public void testCreateIdNumber() {<br><br>&nbsp; <br>&nbsp; Map<String, Object> variables = new HashMap<String, Object>();<br>&nbsp; Stappi stI = new Stappi();<br>&nbsp;&nbsp;&nbsp;&nbsp; variables.put("stappi", stI);<br> <br>&nbsp;&nbsp;&nbsp;&nbsp; RuntimeService runtimeService = activitiRule.getRuntimeService();<br>&nbsp; runtimeService.startProcessInstanceByKey("part2CreateIdNumber", variables);<br>&nbsp; <br>&nbsp; Map<String, String> formProperties = new HashMap<String, String>();<br>&nbsp; formProperties.put("IdNumber", "123456789");<br>&nbsp; <br>&nbsp; TaskService taskService = activitiRule.getTaskService();<br>&nbsp; Task task = taskService.createTaskQuery().singleResult();<br>&nbsp; FormService formService = activitiRule.getFormService();<br>&nbsp; <br>&nbsp; formService.submitTaskFormData(task.getId(), formProperties);<br>&nbsp; <br> <br>&nbsp; // view history query for form properties<br>&nbsp;&nbsp;&nbsp; List<HistoricDetail> historyVariables = activitiRule.getHistoryService()<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .createHistoricDetailQuery()<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .variableUpdates()<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .orderByVariableName()<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .asc()<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .list();<br><br>&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; assertNotNull(historyVariables);<br><br>&nbsp;&nbsp;&nbsp; assertEquals(2, historyVariables.size());<br>&nbsp;&nbsp;&nbsp; HistoricVariableUpdate stAppup= ((HistoricVariableUpdate) historyVariables.get(1));<br><br>&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; assertEquals("studentAppInfo", stAppup.getVariableName());<br>&nbsp;&nbsp;&nbsp; Stappi saii = (Stappi) stAppup.getValue();<br><br>&nbsp;&nbsp;&nbsp; assertEquals("123456789", saii.getIdNumber());<br>&nbsp;&nbsp; <br>&nbsp; System.out.println("CreateIdNumberTest was successful");<br> }<br>}

frederikherema1

But I don't know how I fixed this. But it was activiti specific.

If you don't know how you fixed it, how can you know it's Activiti is causing JUnit to use old version of test-classes? Please don't just assume because you're using activiti, it's the cause of all issues you encounter, especially one JUnit related…