Hi Pavel,

thanks for your reply.

I understand that code coverage differs in some cases. But that's not really my problem.

I can give you an example: TeamCity tells me, that a testcase XY was successful. This testcase uses an instance of class A. But the EMMA coverage report tells me, that class A is not covered (class-coverage). And some buils later, the EMMA coverage report tells me, that the class is covered...that's really confusing...

Markus

Right now I'm running into OutOfMemoryErros when using EMMA...let's switch to IDEA coverage!

Actually, I tried to use IDEA code coverage, but I get the following log error:

Publishing artifacts

Do I have to install additional packages/plugins to get that to work? Or do I miss some configuration parameters? Perhaps I have to put coverage.ic into my artifacs?

(I'm using TeamCity 5.0.2)

Regards,

Markus

Hi Pavel,

hm, I would prefer not to send my build log (it really contains sensitive data). But I can provide the part of my ANT-Buildfile which is used in the run-configuration (I've attachted it).

In my build log, I see the following line right when the runTests-target is called:

[runTests] IDEA Coverage: Java agent added to JUnit task

But after the tests did run, I still get the error:

...

[07:29:26]: [antcall] clean

First, I used the default "*" as include pattern and none as exclude pattern.

Then I tried to use one of my package names as include pattern, which really contains classes: "company.project.*"

As exclude pattern, I used the package name which contained the tests: "company.project.unitTests.*"

Unfortunately, I had the same error result.

Great!

Using junit with fork="yes" solved the issue!

Thank you very much for your help.