I like the second option: viewing the UnitTest SDT as more general with a "testType"
attribute (which would, of course, be optional and accessible from the pMap).
Cheers,
Philip
--On Thursday, November 17, 2005 12:06 AM -1000 Aaron Kagawa <[EMAIL
PROTECTED]> wrote:
Hey Guys,
Is JUnit tests only for Unit Tests? What about System Tests, Integration Tests,
etc?
In a couple of my projects we have separate packages that use Junit for
different
"purposes". Thus, when I send Junit data to Hackystat the data looks as though
(because of the UnitTest Sensor Data Type) they are all "Unit Tests".
Currently, the
only way to distinguish between the different types of tests is to try to
remember the
package names.
So, my question is, should I implement a totally different Sensor Data Type to
accommodate the different types of testing data I have or should the UnitTest
Sensor
Data Type become more general? The latter is probably the better solution. To
make it
more general, we could add a "testType" attribute to the SDT and refactor the
DailyProjectUnitTest to provide information for each type.
comments?
thanks, aaron
