Tests summary

This page summarises information for results of test cases for Last 25 builds in Sync - SYNC - Default Job.

Test	Times broken	Most recent builds
Should test first in new tx History	2	8
Should test first in no transaction History	2	8
Should test all in same tx History	2	8
Should test first throws exception History	2	8
Should test second in new tx History	2	8
Should test both in new tx History	2	8
Should test second throws exception History	2	8
Should delete only the states given History	2	8

Test	Average number of builds to fix
Should test first in no transaction org.openmrs.module.sync.api.db.hibernate.HibernateSyncInterceptorTransactionTest	2
Should test first in new tx org.openmrs.module.sync.api.db.hibernate.HibernateSyncInterceptorTransactionTest	2
Should test second throws exception org.openmrs.module.sync.api.db.hibernate.HibernateSyncInterceptorTransactionTest	2
Should test both in new tx org.openmrs.module.sync.api.db.hibernate.HibernateSyncInterceptorTransactionTest	2
Should test all in same tx org.openmrs.module.sync.api.db.hibernate.HibernateSyncInterceptorTransactionTest	2
Should test first throws exception org.openmrs.module.sync.api.db.hibernate.HibernateSyncInterceptorTransactionTest	2
Should test second in new tx org.openmrs.module.sync.api.db.hibernate.HibernateSyncInterceptorTransactionTest	2
Should delete only the states given org.openmrs.module.sync.scheduler.CleanupSyncTablesTaskTest	2

Test	Average duration (seconds)*
Should create patient from existing user	5 seconds
Get timeout should not throw NPEwhen timeout global property is not set	4 seconds
Should create program	4 seconds
Should save concept set	3 seconds
Should merge patients	3 seconds
Should save current server settings	3 seconds
Should edit patient identifiers	3 seconds
Should edit patient	3 seconds
Should sync an object that is created along with Amap of elements	3 seconds
Should add existing concept to existing set	3 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.