Tests summary

This page summarises information for results of test cases for Last 25 builds in OpenMRS Core - OpenMRS Core 1.10.x - Integration Tests.

Test	Times broken	Most recent builds
Should save last execution time History	2	531, 506
Save order should throw ambiguous order exception if disconnecting multiple active orders for the given concepts History	1	523
Save task should save task to the database History	1	531
Should not throw exception when task definition is null History	1	531
Should not allow task execute to run before initialization is complete History	1	531
Validate should fail validation if class is not accessible History	1	531
Validate should fail validation if name is null or empty or whitespace History	1	531
Validate should pass validation if all required fields have proper values History	1	531
Validate should fail validation if class is not instance of task History	1	531
Validate should fail validation if class not found History	1	531

Test	Average number of builds to fix
Should save last execution time org.openmrs.scheduler.SchedulerServiceTest	1
Save order should throw ambiguous order exception if disconnecting multiple active orders for the given concepts org.openmrs.api.OrderServiceTest	1

Test	Average duration (seconds)*
Form backing object should return valid location given valid location id	22 seconds
Get default locale should not return null if global property does not exist	18 seconds
Should upgrade from clean1 9to1 10	7 seconds
Should convert orderers to being providers instead of users	7 seconds
Should pass if all existing drug order units and frequencies are mapped to concepts	7 seconds
Should migrate drug orders	6 seconds
Should concatenate dose strength and units	5 seconds
Should pass if there are any order types in the database other than drug order type and the new columns exist	5 seconds
Should set values to null if units or frequency blank	5 seconds
Should create discontinuation order for stopped orders	5 seconds

* average duration is calculated based on the entire history of this test.

The chart below shows the number of tests across time. This provides a rough indication of the level of testing over time for the build.