BIND 10 #1290: initial setup of system tests with cucumber

[BIND 10 Development]

#1290: initial setup of system tests with cucumber
-------------------------------------+-------------------------------------
                   Reporter:  jelte  |                 Owner:  jelte
                       Type:  task   |                Status:  reviewing
                   Priority:  major  |             Milestone:
                  Component:         |  Sprint-20111108
  Unclassified                       |            Resolution:
                   Keywords:         |             Sensitive:  0
            Defect Severity:  N/A    |           Sub-Project:  DNS
Feature Depending on Ticket:         |  Estimated Difficulty:  9
        Add Hours to Ticket:  0      |           Total Hours:  0
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by stephen):

 * owner:  stephen => jelte


Comment:

 Reviewed commit b03d29677700c1dd2a527dafe9987defb7556e97

 >> What is the "bind10 main script"?
 > '<prefix>/bin/bind10'. Change it to 'executable'?
 Or program.  I just thought that "script" was a bit confusing.

 >> ''BIND9_TOP/BIND10_TOP''
 >just take the bind10 from the users path settings.
 I think it unlikely that most people will have bind10 in their current
 path.  However, this is something that can be altered later - we don't
 need to change it now.

 '''tests/lettuce/README.tutorial'''[[BR]]
 One minor thing: the text talks of "of my bind10", but the example that
 follows includes "as b10_second_instance".  The two should match.

 > We probably need some documentation as to what phrases are available.
 > Hmm, yes, probably. Not sure how to do it though, I don't really want to
 retype the entire function description yet again (which will go stale).
 Taking the description from the "@step" decorator doesn't really work
 since, as it includes a regular expression, it can be fairly cryptic.

 I would suggest adding lines giving the lettuce step syntax to the start
 of each of the function descriptions, e.g.
 {{{
 @step('start bind10(?: with configuration (\S+))?' +\
       '(?: with cmdctl port (\d+))?(?: as (\S+))?')
 def start_bind10(step, config_file, cmdctl_port, process_name):
     """
     Start bind10 [with configuration <config_file>]
                  [with cmdctl port <cmdctl_port>]
                  [as <process_name]

     Start BIND 10 with the given optional config file, cmdctl port, and
     store the running process in world with the given process name.
      :
 }}}
 Then write a Python script that goes through the relevant Python files,
 searches for a line beginning "@step", then extracts the all lines from
 the following function header (as delineated by the triple quotes tokens)
 into a separate file.

 Just one minor change to README.tutorial then please merge.  I don't need
 to see it again.

-- 
Ticket URL: <http://bind10.isc.org/ticket/1290#comment:12>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development