BIND 10 #1878: lettuce tests should be more fail safe about runtime environment

[BIND 10 Development]

#1878: lettuce tests should be more fail safe about runtime environment
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  defect        |  UnAssigned
            Priority:  medium        |                       Status:  new
           Component:  build system  |                    Milestone:  Next-
           Sensitive:  0             |  Sprint-Proposed
         Sub-Project:  Core          |                     Keywords:
Estimated Difficulty:  0             |              Defect Severity:  N/A
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 After experiencing 100 times trying to figure out why my lettuce tests
 fail strangely just to remember I need to install the entire system or
 incorporate the setup_intree_bind10 script, I'd now argue this setup
 is so error prone.

 I don't like to include the environments of the setup script in my
 usual shell initialization because it has side effects for non lettuce
 environments.

 My suggestion is to introduce another shell script to run the lettuce
 test like this:

 {{{
 source setup_intree_bind10.sh
 export LETTUCE_SETUP_COMPLETED=1
 lettuce
 }}}

 and somewhere in features/terrain check the LETTUCE_SETUP_COMPLETED
 variable, and if it's undefined abort the test with a warning.

 This way we don't have to pollute the non-test environment, don't have
 to install the system beforehand, and can know what's wrong if we
 don't run the test from the script.

-- 
Ticket URL: <http://bind10.isc.org/ticket/1878>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development