GeekArticles
Testing
Test Approach
Testing
Test ApproachUnit-Testing Hibernate With HSQLDB
I've used lots of methods to transform data between databases and object code. From hand-coded SQL to JDO to EJB. I've never found a method I liked particularly well. This distaste has become especially acute since adopting test-driven development (TDD) as a guiding philosophy.
Unit-testing should have as few barriers as possible. For relational databases those barriers range from external dependencies (is the database running?) to speed to keeping the relational schema synchronized with your object model. For these reasons it is vital to keep database access code away from the core object model and to test as much as possible without touching a real database.
Sponsored Links
Read Next: Test Automation Snake Oil
Related Topics
Subscribe via RSS
Test Approach
- Software-Based Memory Testing
- Improving Requirements Through Testing
- Requirements Patterns via Events / Use Cases
- A New Test Approach to Software Testing
- The Definition of Quality Assurance
- Is Quality Assurance A Discipline
- Organisational Approaches for Testing
- Automation test tools
- Unit-Testing Hibernate With HSQLDB
- Test Automation Snake Oil
