Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#10 Test output configuration -- logging to a file (instead of stdout).

open
5
2014-04-26
2013-11-29
Michael L. Rilee
No

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).

Related

Feature Requests: #10

Discussion

    • labels: --> OutputFormat, LogFile
     
  • Another aspect is the command line redirection of STDOUT.

     
    • labels: OutputFormat, LogFile --> OutputFormat, LogFile, CommandLineRedirection
     
  • Does the command line option "-o <outputfile> Direct pFUnit messages to a file." satisfy this feature request?

    Also, has anyone exercised this option?

     
    • Tom Clune
      Tom Clune
      2014-04-26

      On Apr 26, 2014, at 4:12 PM, "Michael L. Rilee" mlrilee@users.sf.net wrote:

      Does the command line option "-o Direct pFUnit messages to a file." satisfy this feature request?

      I believe so. Can't remember who the original request came from, but I think it was Sean.

      Also, has anyone exercised this option?

      I've used it, but perhaps not recently.

      [feature-requests:#10] Test output configuration -- logging to a file (instead of stdout).

      Status: open
      Group: Current Release Upgrade (v2)
      Labels: OutputFormat LogFile CommandLineRedirection
      Created: Fri Nov 29, 2013 05:06 PM UTC by Michael L. Rilee
      Last Updated: Thu Dec 05, 2013 04:35 AM UTC
      Owner: Michael L. Rilee

      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).

      Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/pfunit/feature-requests/10/

      To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

      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: #10

      Attachments