[#LOGCXX-23] Unit tests have become stale

Log4cxx

Unit tests have become stale

Created: 09/Oct/04 02:19 PM Updated: 14/Oct/04 05:57 PM

Return to search

Component/s:

None

Affects Version/s:

0.9.7

Fix Version/s:

0.10.0

Time Tracking:

Not Specified

Resolution Date:

14/Oct/04 05:57 PM

Description

« Hide

log4cxx comes with a decent amount of unit tests, but how to run them hasn't been apparent to me. When getting the unit tests running from an Ant build (see related bug), there are on the order of 15 failures. I'm still investigating but at least some of them are due to the tests not being updated to keep in sync with the code base.

The most obvious old test are in xmllayouttest where log4cxx outputs class and module attributes for locationInfo (currently empty) and the comparison log does not contain them.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

[ Permlink | « Hide ]

Curt Arnold added a comment - 14/Oct/04 05:57 PM

Only the XML layout tests were truly stale. Other tests did have a strict expectation that source file names did not include a path, I added filters (filenamefilter and xmlfilenamefilter) to transform any occurance of the value of __FILE__ to the expected file name. It wasn't apparent to me how to run the tests from the existing make files and am not a make guru. In the Ant build file added in issue ~~LOGCXX-25~~, I included targets that will run the tests.