Challenges and perils of testing database manipulation code
Do you have tests for your database manipulation code? We know the answer. Developers face many challenges. Do integration or unit tests need to be written? Should mocks be implemented or an in-memory database be used? How should a database be reset or repopulated between tests? These are only a few examples. We briefly introduce an Eclipse plugin to analyze database manipulation code and we show examples of interesting prevalent problems in testing this critical code.