Paging & Journal tests will require UnitTests also. There are a few races that I tested using Unittests that would be easier to reproduce them as UnitTests.
In the past we would consider anything using RealFile as an integration test, and that's why we had some common classes between Unit and integration. I will place those PagingTest and JournalTests as UnitTests.
For the easyMock tests:
PagingImplTest: usage is minimal, just creating a NiceMock that I could create an implemented Mock if you really want to get rid of EasyMock. (I'm not doing the upside-down programming style on some of these tests).
Journal: There are a few tests using EasyMock to validate the encoding. I will get rid of those.
I will still keep the FakeJournalUnitTests for now, as they are really easy to debug when things are going wrong during development on the journal.