The other [useful addition to test output] would be a status report that goes to, say, a log file instead of stdout, and ideally is easy for a script to read. The idea being that if you have a really big code base with multiple components (like CESM), and you're going to have many pFUnit executables, you can have some script come along afterward and produce a summary of test status, and not be foiled by weird output (e.g. a routine in the SUT that prints
"OK" to unit 6 for some reason).
Another aspect is the command line redirection of STDOUT.
Does the command line option "-o <outputfile> Direct pFUnit messages to a file." satisfy this feature request?
Also, has anyone exercised this option?
On Apr 26, 2014, at 4:12 PM, "Michael L. Rilee" mlrilee@users.sf.net wrote:
I believe so. Can't remember who the original request came from, but I think it was Sean.
I've used it, but perhaps not recently.
Thomas Clune, Ph. D. Thomas.L.Clune@nasa.gov
CISTO Code 606.0
NASA GSFC 301-286-4635
MS 610.8 B33-C128
Greenbelt, MD 20771
Related
Feature Requests:
#10Functionality exists as of 3.0.