Refactoring: improving the design of existing code
Refactoring: improving the design of existing code
Test Driven Development: By Example
Test Driven Development: By Example
Agile Database Techniques: Effective Strategies for the Agile Software Developer
Agile Database Techniques: Effective Strategies for the Agile Software Developer
Test Driven development: A Practical Guide
Test Driven development: A Practical Guide
Threat Modeling
Refactoring Databases: Evolutionary Database Design
Refactoring Databases: Evolutionary Database Design
Refactoring information systems: association folding and unfolding
ACM SIGSOFT Software Engineering Notes
ADNTIIC'10 Proceedings of the First international conference on Advances in new technologies, interactive interfaces, and communicability
Critical issues on test-driven development
PROFES'11 Proceedings of the 12th international conference on Product-focused software process improvement
A test case refactoring approach for pattern-based software development
Software Quality Control
| Hi-index | 0.00 |
Developers can use a test-driven development with database schema just as they use it with application code. Implementing test-driven database development (TDDD) involves three relatively simple steps: database refactoring, database regression testing, and continuous database integration. In database refactoring, developers make a simple change to a database to improve the design without changing its semantics. In database regression testing, they run a comprehensive test suite that validates the database regularly-ideally, whenever developers change the database schema or access the database in a different way. In continuous database integration, developers rebuild and retest the database schema whenever it changes. From a technical viewpoint, TDDD is straightforward. However, cultural challenges can make it difficult to adopt.