Previously we were not loading the status from the database when you updated the JobExecution.  Because of that, we would overwrite any updates that were made behind the scenes with what the current BathStatus was.  Now that isn't the case.  Now, we're updating the status with whatever is in the database before saving it.

If we take the example of Spring Batch Admin.  I kick off a job.  It's running normally.  Spring Batch Admin updates the status in the database to STOPPED.  Before, this wouldn't get picked up at this point, it would get picked up at a different point in the lifecycle.

So my question is…do we have any test cases that address the scenario described above to make sure that the status is honored (in the case I'm describing, that the next step isn't started)?