[hijack]
I don't have an answer to your question, but I am doing something simular and my logging is not sequentially equivalent to the test. Do you have simular results?
I asked a question a few threads ago whether or not test cases are guarenteed to run sequentially or not and have heard that they are. So, there is some problem with writing to streams during tests. Wondered if you encountered the same thing or have ideas on overcoming the problem.
[end hijack]
I think it would be easier to have some built in logging methods for the test fixures themselves.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
Sorry if the answer is supposed to be obvious; I did look through the documentation and examples, but couldn't find it.
Question: What's the "preferred" method for outputting (to STDOUT, etc.) diagnostic messages during the test's execution?
These are interim, diagnostic messages, not test results.
Currently I'm using a logging library (log4cxx), which does this work me. I'm not sure whether cppunit offers me any alternatives.
Should cppunit have any diagnostic output functions / macros? Probably not (separation of concerns). I'd love to know your opinion.
Many thanks,
Paul
[hijack]
I don't have an answer to your question, but I am doing something simular and my logging is not sequentially equivalent to the test. Do you have simular results?
I asked a question a few threads ago whether or not test cases are guarenteed to run sequentially or not and have heard that they are. So, there is some problem with writing to streams during tests. Wondered if you encountered the same thing or have ideas on overcoming the problem.
[end hijack]
I think it would be easier to have some built in logging methods for the test fixures themselves.