[1290] rename example feature itself too

tests/lettuce/features/example.feature

@@ -1,4 +1,4 @@
-Feature: SQLite3 backend
+Feature: Example feature
     This is an example Feature set. Is is mainly intended to show
     our use of the lettuce tool and our own framework for it
     The first scenario is to show what a simple test would look like, and

tests/lettuce/features/terrain/bind10_control.py

@@ -29,7 +29,6 @@ def start_bind10(step, config_file, cmdctl_port, process_name):
     world.processes.add_process(step, process_name, args)
 
     # check output to know when startup has been completed
-    # TODO what to do on failure?
     message = world.processes.wait_for_stderr_str(process_name,
                                                   ["BIND10_STARTUP_COMPLETE",
                                                    "BIND10_STARTUP_ERROR"])

tests/lettuce/features/terrain/querying.py

@@ -12,14 +12,17 @@ import re
 # the result will be stored in last_query_result, which can then be inspected
 # more closely, for instance with the step
 #
-# last query should have <property> <value>
+# "the last query response should have <property> <value>"
 #
+# Also see example.feature for some examples
 
 #
 # define a class to easily access different parts
 # We may consider using our full library for this, but for now
 # simply store several parts of the response as text values in
-# this structure
+# this structure.
+# (this actually has the advantage of not relying on our own libraries
+# to test our own, well, libraries)
 #
 # The following attributes are 'parsed' from the response, all as strings,
 # and end up as direct attributes of the QueryResult object: