Skip to content
Snippets Groups Projects
Select Git revision
  • fc4b9be4d63fd7ac65a9a3e5774c16e984d405a8
  • master default protected
2 results

test_fsig.py

Blame
    • Daniel Brown's avatar
      4d173029
      adding in fsig command (not parsing yet). See example test_fsig.py in bin... · 4d173029
      Daniel Brown authored
      adding in fsig command (not parsing yet). See example test_fsig.py in bin folder. Also made component variable an optional argument for xaxis and x2axis which will break previous scripts. Did this as when setting the parameter to tune, the Param object contains whatever component owns that parameter so no need to pass it twice. Also stops someone passing a parameter not for the component stated.
      4d173029
      History
      adding in fsig command (not parsing yet). See example test_fsig.py in bin...
      Daniel Brown authored
      adding in fsig command (not parsing yet). See example test_fsig.py in bin folder. Also made component variable an optional argument for xaxis and x2axis which will break previous scripts. Did this as when setting the parameter to tune, the Param object contains whatever component owns that parameter so no need to pass it twice. Also stops someone passing a parameter not for the component stated.
    verifymsg 1.00 KiB
    # The "verifymsg" file is used to allow verification of logging
    # information.  It works best when a template (as specified in the
    # rcsinfo file) is provided for the logging procedure.  Given a
    # template with locations for, a bug-id number, a list of people who
    # reviewed the code before it can be checked in, and an external
    # process to catalog the differences that were code reviewed, the
    # following test can be applied to the code:
    #
    #   Making sure that the entered bug-id number is correct.
    #   Validating that the code that was reviewed is indeed the code being
    #       checked in (using the bug-id number or a seperate review
    #       number to identify this particular code set.).
    #
    # If any of the above test failed, then the commit would be aborted.
    #
    # Actions such as mailing a copy of the report to each reviewer are
    # better handled by an entry in the loginfo file.
    #
    # One thing that should be noted is the the ALL keyword is not
    # supported.  There can be only one entry that matches a given
    # repository.