IN PROGRESS - BATCH-962: refactor TaskletStep's exception handling for better clarity

cleaned up redundant metadata updates from AbstractStep

spring-batch-core/src/test/java/org/springframework/batch/core/step/AbstractStepTests.java

@@ -291,7 +291,7 @@ public class AbstractStepTests {
 		assertEquals("close", events.get(i++));
 		assertEquals(3, events.size());
 
-		assertEquals(ExitStatus.UNKNOWN.getExitCode(), execution.getExitStatus().getExitCode());
+		assertEquals(ExitStatus.UNKNOWN, execution.getExitStatus());
 	}
 
 	/**

spring-batch-core/src/test/java/org/springframework/batch/core/step/item/TaskletStepExceptionTests.java

@@ -130,7 +130,7 @@ public class TaskletStepExceptionTests {
 		taskletStep.execute(stepExecution);
 		assertEquals(COMPLETED, stepExecution.getStatus());
 		assertFalse(stepExecution.getFailureExceptions().contains(exception));
-		assertEquals(4, jobRepository.getUpdateCount());
+		assertEquals(3, jobRepository.getUpdateCount());
 	}
 
 	@Test

spring-batch-core/src/test/java/org/springframework/batch/core/step/tasklet/TaskletStepTests.java

@@ -298,8 +298,7 @@ public class TaskletStepTests {
 		step.execute(stepExecution);
 
 		// context saved before looping and updated once for every processing
-		// loop (once in this case) and finally in the abstract step (regardless
-		// of execution logic)
+		// loop (once in this case) 
 		assertEquals(3, list.size());
 	}