Bugzilla – Bug 5614
TCK expects JobExecution to be updated as job runs
Last modified: 2014-01-03 03:42:22 UTC
This is essentially re-opening of 5371. The TCK expects that a JobExecution is being updated behind the scenes instead of getting a new instance before checking the state. The list below is what I have currently identified and will add tests to this list as I find more.
My guess is that most of the places JobOperatorBridge#*AndWaitForResult are called will need updates.
Fixed all these and will also mention that I found another similar issue with the testInvokeJobWithUserStopAndRestart() test.
If we're going to look at the BatchStatus before waiting for a terminating status, then we should allow we might see a status of STARTING (we'd been expecting STARTED). Fixed this as well.