Comments on: Getting Coverage For Integration Tests http://blog.jayway.com/2008/12/13/getting-coverage-for-integration-tests/ Sharing Experience Sun, 12 Feb 2012 05:23:29 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Andrew http://blog.jayway.com/2008/12/13/getting-coverage-for-integration-tests/comment-page-1/#comment-44804 Andrew Thu, 01 Jul 2010 23:27:17 +0000 http://blog.jayway.com/?p=565#comment-44804 Wondering, in the case of driver type classes, what the business value is in creating a set of jUnits to cover code what is already 100% covered by Integration Tests? If it works against the 'real thing' why manufacture a set of mocks just to claim coverage under jUnits? This does not seems smart to me. Wondering, in the case of driver type classes, what the business value is in creating a set of jUnits to cover code what is already 100% covered by Integration Tests? If it works against the ‘real thing’ why manufacture a set of mocks just to claim coverage under jUnits? This does not seems smart to me.

]]> By: Charlie http://blog.jayway.com/2008/12/13/getting-coverage-for-integration-tests/comment-page-1/#comment-33783 Charlie Wed, 14 Apr 2010 21:42:04 +0000 http://blog.jayway.com/?p=565#comment-33783 Nice example, I didn't know about this maven plugin. But what if I need to start cargo before test phase for example? Maven doesn't package the jar during test phase but cargo need this... Nice example, I didn’t know about this maven plugin.
But what if I need to start cargo before test phase for example?
Maven doesn’t package the jar during test phase but cargo need this…

]]> By: Doug http://blog.jayway.com/2008/12/13/getting-coverage-for-integration-tests/comment-page-1/#comment-25215 Doug Mon, 15 Feb 2010 20:36:28 +0000 http://blog.jayway.com/?p=565#comment-25215 What if your integration tests are running against a package? Then the runtime won't be instrumented by cobertura... What if your integration tests are running against a package?
Then the runtime won’t be instrumented by cobertura…

]]> By: Ulrik Sandberg http://blog.jayway.com/2008/12/13/getting-coverage-for-integration-tests/comment-page-1/#comment-8644 Ulrik Sandberg Tue, 28 Jul 2009 07:54:30 +0000 http://blog.jayway.com/?p=565#comment-8644 You're absolutely right. Unit tests and integration tests should not be mixed together, which is the reason I placed the integration tests in a separate profile. However, there is value in being able to see the overall coverage number, since that will immediately show you code that is not tested at all. Normally, however, you should focus on the coverage of the unit tests. You’re absolutely right. Unit tests and integration tests should not be mixed together, which is the reason I placed the integration tests in a separate profile. However, there is value in being able to see the overall coverage number, since that will immediately show you code that is not tested at all. Normally, however, you should focus on the coverage of the unit tests.

]]> By: Lars Tackmann http://blog.jayway.com/2008/12/13/getting-coverage-for-integration-tests/comment-page-1/#comment-8643 Lars Tackmann Tue, 28 Jul 2009 07:44:31 +0000 http://blog.jayway.com/?p=565#comment-8643 Great article - I am wondering though if we really need code coverage for integration tests and if it such a good idea to mix it with the unit tests coverage. Usually when high coverage can only be obtained with integration tests it is a sign that the code is ill designed. Personally I prefer making sure that all my JMS/SQL (dao) code is tested and this usually means integrations tests. For the business logic I prefer to make sure that the unit tests are run by the unit tests and not by the integrations tests. Great article – I am wondering though if we really need code coverage for integration tests and if it such a good idea to mix it with the unit tests coverage.

Usually when high coverage can only be obtained with integration tests it is a sign that the code is ill designed. Personally I prefer making sure that all my JMS/SQL (dao) code is tested and this usually means integrations tests.

For the business logic I prefer to make sure that the unit tests are run by the unit tests and not by the integrations tests.

]]> By: Ulrik Sandberg http://blog.jayway.com/2008/12/13/getting-coverage-for-integration-tests/comment-page-1/#comment-7044 Ulrik Sandberg Fri, 26 Jun 2009 19:54:58 +0000 http://blog.jayway.com/?p=565#comment-7044 You should run "mvn eclipse:eclipse -Pitcov". You should run “mvn eclipse:eclipse -Pitcov”.

]]> By: Cameron http://blog.jayway.com/2008/12/13/getting-coverage-for-integration-tests/comment-page-1/#comment-7017 Cameron Fri, 26 Jun 2009 10:45:10 +0000 http://blog.jayway.com/?p=565#comment-7017 How do you edit those src/java/it files in your IDE .. since they aren't on the default build path ? How do you edit those src/java/it files in your IDE .. since they aren’t on the default build path ?

]]>