http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660I have this two levels of tests too. Usually the unit test mock the next layer (example testing Business Layer and mock the Data Access Layer). In the integration test I will run some database scripts to create the database initial state and run the integration tests that will do on Business layer and I will not mock the DAL. The test will go to the end of the chain .. to the database. this is the way that I do.. and that's why the integration tests take more time then the unit tests (in my case). Regards Paulo Aboim Pinto Odivelas - Portugal http://ayende.com/4003/unit-tests-vs-integration-tests#comment4http://ayende.com/4003/unit-tests-vs-integration-tests#comment4Mon, 11 May 2009 01:18:54 GMTJohn, That number also include the time to spin up the test framework, but yes, they are oing a lot http://ayende.com/4003/unit-tests-vs-integration-tests#comment3http://ayende.com/4003/unit-tests-vs-integration-tests#comment3Sun, 10 May 2009 13:48:03 GMTAnd you are right. Moreover, every newbie in the test driven approach going to write the integration tests in first order. Especially if he is not strong enough in OOD and his design is like a one big transaction script with GOTOs :) http://ayende.com/4003/unit-tests-vs-integration-tests#comment2http://ayende.com/4003/unit-tests-vs-integration-tests#comment2Sun, 10 May 2009 13:48:00 GMTAm I the only one that finds it shocking that 65 unit tests took 7.49 seconds to run? Based on that timing it sounds like the unit tests may be doing more than expected. I'm used to 65 unit tests taking a fraction of a second. What kind of work are your unit tests doing? It almost seems like they would need some level of "integration" to make them that slow. http://ayende.com/4003/unit-tests-vs-integration-tests#comment1http://ayende.com/4003/unit-tests-vs-integration-tests#comment1Sun, 10 May 2009 13:37:01 GMT