Bug 5655 - ChunkTests for skipping writes don't go far enough
ChunkTests for skipping writes don't go far enough
Status: RESOLVED MOVED
Product: jbatch
Classification: Unclassified
Component: TCK
1
All All
: P5 normal
: ---
Assigned To: ScottKurz
tck_future
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-12-18 19:50 UTC by mminella
Modified: 2015-09-03 14:24 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mminella 2013-12-18 19:50:21 UTC
ChunkTests#testChunkSkipWrite and ChunkTests#testChunkSkipWriteExceedSkip verify that the list the SkipWriteListener receives does not have any nulls in it, but it does not verify the number of items in the list (or that the items are the correct ones for that matter).  We noticed this on accident by just wrapping the Spring Batch equivalent of this listener.  In SB, by default, we only pass in the item that was skipped (instead of all of the items in the current chunk as the spec requires).  When we wrap the SB functionality (passing a new list that contains only the skipped item to the listener), the test passes even though the implemented behavior is incorrect.
Comment 1 ScottKurz 2015-09-03 14:24:51 UTC
Moving to:
https://github.com/WASdev/standards.jsr352.tck/issues/5