I am looking at creating a *LOB viewer plugin to allow *LOB columns to be rendered based on the content (initially serialized Java classes but ideally extensible to other types). I have a start to this but before I get much further, is there a specific pattern for implementing unit tests to handle DB calls? Basically, is there any mechanism for an in-memory DB (like H2) specifically for use during test runs? I saw that SQuirreL uses easymock but if there is something that has been built to use as a SQL-compliant DB during testing, I would definitely prefer to use that.
"We can't solve problems by using the same kind of thinking we used when we created them." - Albert Einstein