Two things for this test:
1) The KeyRange.getKeyRange method will force lowerInclusive to false when the lowerBound is UNBOUND and upperInclusive to false when the upperBound is UNBOUND
2) This scenario won't happen currently (an unbounded range followed by anything else) because we stop building the scanRanges if we encounter an unbounded range.

It's still a good idea to consider the unbound cases, though. If anything, there might be special cases in that hairy code base on a range being unbound. Think about that a bit and maybe add some more tests around it.