Specification in order to write the right test?

Ask OpenMRS
#1

Method

	@Override
	public PatientProgram unvoidPatientProgram(PatientProgram patientProgram) {
		Date voidDate = patientProgram.getDateVoided();
		patientProgram.setVoided(false);
		for (PatientState state : patientProgram.getStates()) {
			if (voidDate != null && voidDate.equals(state.getDateVoided())) {
				state.setVoided(false);
				state.setVoidedBy(null);
				state.setDateVoided(null);
				state.setVoidReason(null);
			}
		}
		return Context.getProgramWorkflowService().savePatientProgram(patientProgram); // The savePatientProgram method handles all of the unvoiding defaults
	}

of class org.openmrs.api.impl.ProgramWorkflowServiceImpl empties all the ‘voided’ fields in patientState but does not empty voidedBy, dateVoided and voidReason in patientProgram.

How can I know if that is correct? Is there some kind of specification I could consult in order to write the right test?

#2

Write a test which confirms that those fields are automatically emptied for you.

#3

Doesn’t work for the …ServiceUnitTest class since it just uses mocks.

But yes, in the …ServiceTest class extending SpringContextTests RequiredDataAdvice seems to kick in calling BaseUnvoidHandler which empties the fields and also calls setVoided(false). Very reassuring.:slight_smile:

#4

I like the assurance. :smile: