testng + inspection

teamcity (1.2) is now running nicely - I only have 2 problems:

1. when clicking the codeinspection build result link, this can take a VERY long time.
and if I decide to cancel it (by closing the browser tab for example), this seems not to work, I still have to wait a long time until the teamcity pages respond again.
would be perfect if you could somehow speed up this

2. I can view the testng results (index.html) via the artifacts link.

But it would be really nice to have some better integration, like for code coverage,
so that directly on the main result page I could see something like this:
41 tests run
2 tests failed

- is this possible with JUnit?
- is this possible somehow with testng?

8 comments
Comment actions Permalink

Michael Damberger wrote:

teamcity (1.2) is now running nicely - I only have 2 problems:

1. when clicking the codeinspection build result link, this can take a VERY long time.
and if I decide to cancel it (by closing the browser tab for example), this seems not to work, I still have to wait a long time until the teamcity pages respond again.
would be perfect if you could somehow speed up this


Inspection storage and reporting was completely rewritten in TC 2.0
which is available in EAP and will be released in the March'07. Please
note that previous inspection information will be lost on upgrade.
(If you decide to try it please backup your DB and .buildserver to be
able to downgrade to 1.2)

--
Alexey Gopachenko
JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

0
Comment actions Permalink

Michael,

2. I can view the testng results (index.html) via the
artifacts link.


I'm slightly confused, testng results should be available in the same way as for JUnit.
Which build runner do you use?
You should be able to view failing tests count on the main page - we use it for our builds for Ant runner.

Regards,
KIR

0
Comment actions Permalink

Thanks for the reply. Great news that it should work - now I just need to find out how ;)

-> I use the ant build runner

this is the ant target for the tests. Maybe I need junit output format?

]]>
<arg line="-d $ -sourcedir $/test/src $/test/testng.xml"></arg>
</java>

0
Comment actions Permalink

We add runtime listener to TestNG, so it shoudn't depend on format.
I'd appreciate if you file a Jira issue with you build logs and debug infromation from build agent as described at http://www.jetbrains.net/confluence/display/TW/HowtoDebug+problems

One possible reason is that we didn't support JDK1.4 properly in this case, but we should check this.

Kind regards,
KIR

0
Comment actions Permalink

We add runtime listener to TestNG


how does this work when testng is started via forked java?
I will try to deliver the debug infos...

0
Comment actions Permalink

I'm blind. This won't work when starting testNG your way.
We support only testng task in Ant :(

0
Comment actions Permalink

Thanks for the info. I will try to use the testng task then...

0
Comment actions Permalink

ok, this works now:

Build agent: * Tests failed: 1 (1 new), passed: 20

Wow, live status of failed and passed tests. Good work, guys!! :)

0

Please sign in to leave a comment.