Ticket #138 (closed defect: invalid)

Opened 2 years ago

Last modified 6 months ago

Integration test log4j default config and minor cleanup

Reported by: ebrown Assigned to: ebrown
Priority: medium Milestone:
Component: topaz-testing Version: 0.8
Keywords: testing Cc:
Blocking: Blocked By:

Description

If integration tests are run without a default log4j.properties in either:

  • ~/.m2/topaz/container-classes
  • ${basedir}/src/it/container-classes

If one of these do not exist, default logging is a bit screwy -- even missing sometimes.

Also, Pradeep suggested using a ${topaz.home}/container-classes instead of ~/.m2/topaz/... And then put ${topaz.install.dir} under that. This is a good idea.

Also, not clear if or how it might be possible to have different log4j configuration for container/webapps and test classes themselves in src/it/java. In fact, it appears that any configuration for one impacts (possibly overriding) the other.

This ticket would finalize ideas started in #122 (getting log4j working for testing).

Dependency Graph

Change History

06/19/07 16:12:20 changed by amit

  • version changed from 0.5-SNAPSHOT to 0.8.
  • milestone changed from TBD to 0.8.

Is this something we need to think about as part of the testing framework?

06/20/07 12:02:44 changed by amit

  • priority changed from unassigned to medium.

07/04/07 01:30:53 changed by ebrown

  • status changed from new to closed.
  • resolution set to invalid.

This is not a concern with the PlosTestFramework? as it uses the logging configured via the rpms.

07/16/08 11:00:34 changed by

  • milestone deleted.

Milestone 0.8 deleted