Also, Version 6 the property 'junit.sensor.enabled' somehow snuck in. I'm not
sure why it's there, but I'd like to get rid of it in Version 7.
In V6 this is used on hackydev integration build. There are several
configurations, but sensor.properties file is global to all configurations.
Does that mean we want to send junit sensor data from all configurations on
hackydev? Thanks. -Cedric
Philip Johnson wrote:
----- Original Message -----
From: Julie Ann Sakuda <[EMAIL PROTECTED]>
Date: Friday, November 25, 2005 6:39 pm
Subject: [CSDL-LOCAL-L] Daily Build not sending Junit data
To: [EMAIL PROTECTED]
Hi all,
Aaron mentioned to me earlier today that it didn't look like
JUnit
data was being sent to Hackystat. In junit.build.xml I wrote a
hackyCore_Build.junit.hackystat.sensor task which sends the JUnit
data
to Hackystat. However, this task never gets called as of now.
Should the sending of data be integrated into the JUnit Report
macros,
so data is sent per module?
In Version 7, JUnitReport is only executed on a module when there is a unit
test failure in that module (otherwise, the report doesn't say much of
interest, and JUnitReport is expense to run, time-wise).
So, integrating the JUnitSensor into JUnitReport is not the way to go, because we want unit test sensor data to be sent whenever unit tests are run, not just when some fail.
Also, Version 6 the property 'junit.sensor.enabled' somehow snuck in. I'm not sure why it's there, but I'd like to get rid of it in Version 7. The sensor already checks the sensor.properties file to see whether it should run or not; I don't currently see any reason to add an additional version of the variable in the build file.
I've committed a minor fix to junit.build.xml, but I need to think a bit
further about how to integrate JUnit into the macros. Worst case, we need to
call antcall, and I want to see if I can think of a way around it (without
having to require the junit sensor to be installed.)
Cheers,
Philip
Cheers,
Philip
