http://www.xaprb.com/blog/2008/08/19/how-to-unit-test-code-that-interacts-with-a-database/ Stay curious! Fri, 12 Mar 2010 03:51:07 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://www.xaprb.com/blog/2008/08/19/how-to-unit-test-code-that-interacts-with-a-database/#comment-17510 Rick Tue, 29 Dec 2009 00:23:40 +0000 http://www.xaprb.com/blog/2008/08/19/how-to-unit-test-code-that-interacts-with-a-database/#comment-17510 Guys, is there any tool to do unit test on MySQL? Thx. Guys,
is there any tool to do unit test on MySQL?
Thx.

]]> http://www.xaprb.com/blog/2008/08/19/how-to-unit-test-code-that-interacts-with-a-database/#comment-17475 Frank Wed, 23 Dec 2009 23:30:04 +0000 http://www.xaprb.com/blog/2008/08/19/how-to-unit-test-code-that-interacts-with-a-database/#comment-17475 One approach we have used successfully was to embed the mysql server into our C++ test executables. At least for the relatively small database that the project included this worked reasonably well. No modifications to the database access layer were necessary and creating a blank database was just a matter of copying some small files into a temporary directory. You loose the ability to easily debug the content of the database, but with some dump-tools this was not a big problem. One approach we have used successfully was to embed the mysql server into our C++ test executables. At least for the relatively small database that the project included this worked reasonably well.
No modifications to the database access layer were necessary and creating a blank database was just a matter of copying some small files into a temporary directory. You loose the ability to easily debug the content of the database, but with some dump-tools this was not a big problem.

]]> http://www.xaprb.com/blog/2008/08/19/how-to-unit-test-code-that-interacts-with-a-database/#comment-17452 Applications et bases de données, comment tester ? « Choses à faire Thu, 17 Dec 2009 09:47:25 +0000 http://www.xaprb.com/blog/2008/08/19/how-to-unit-test-code-that-interacts-with-a-database/#comment-17452 [...] les Mocks peuvent ne pas être appropriés pour les tests d’accès à la base, certains les déconseillent même vivement.Les avantages sont une vitesse d’exécution bien supérieure, en plus de pouvoir tester [...] [...] les Mocks peuvent ne pas être appropriés pour les tests d’accès à la base, certains les déconseillent même vivement.Les avantages sont une vitesse d’exécution bien supérieure, en plus de pouvoir tester [...]

]]> http://www.xaprb.com/blog/2008/08/19/how-to-unit-test-code-that-interacts-with-a-database/#comment-16651 nathanr Fri, 10 Jul 2009 11:09:24 +0000 http://www.xaprb.com/blog/2008/08/19/how-to-unit-test-code-that-interacts-with-a-database/#comment-16651 justinb is spot on unit tests responsibility is to test the actual implementation of a class. Outside/external components that are outside of the control or scope of a codebase is something that gets addressed with integration tests. Were the focus is to exercise interaction between different components whether they are internal or external to a codebase. justinb is spot on unit tests responsibility is to test the actual implementation of a class. Outside/external components that are outside of the control or scope of a codebase is something that gets addressed with integration tests. Were the focus is to exercise interaction between different components whether they are internal or external to a codebase.

]]> http://www.xaprb.com/blog/2008/08/19/how-to-unit-test-code-that-interacts-with-a-database/#comment-15291 The power of a good SQL naming convention at Xaprb Sun, 26 Oct 2008 07:12:43 +0000 http://www.xaprb.com/blog/2008/08/19/how-to-unit-test-code-that-interacts-with-a-database/#comment-15291 [...] Here are a couple of concrete ideas. With the conventions I’ve shown, it’s easy to write a simple recursive program that can examine your entire database for data consistency, based only on naming conventions. And you can easily write a program to dump an account and all its related data (client, employee, and so on) for such purposes as migrating a client to a new shard or creating a dataset for a test suite. [...] [...] Here are a couple of concrete ideas. With the conventions I’ve shown, it’s easy to write a simple recursive program that can examine your entire database for data consistency, based only on naming conventions. And you can easily write a program to dump an account and all its related data (client, employee, and so on) for such purposes as migrating a client to a new shard or creating a dataset for a test suite. [...]

]]>