Browse Source

[1900] Check for CC status before starting inmemory_over_sqlite3.feature

Mukund Sivaraman 13 years ago
parent
commit
c2d70c85d3

+ 1 - 1
tests/lettuce/configurations/inmemory_over_sqlite3/secondary.conf

@@ -4,7 +4,7 @@
         "loggers": [ {
         "loggers": [ {
             "debuglevel": 99,
             "debuglevel": 99,
             "severity": "DEBUG",
             "severity": "DEBUG",
-            "name": "auth"
+            "name": "*"
         } ]
         } ]
     },
     },
     "Auth": {
     "Auth": {

+ 2 - 0
tests/lettuce/features/inmemory_over_sqlite3.feature

@@ -5,6 +5,8 @@ Feature: In-memory zone using SQLite3 backend
 
 
     Scenario: Load and response
     Scenario: Load and response
         Given I have bind10 running with configuration inmemory_over_sqlite3/secondary.conf
         Given I have bind10 running with configuration inmemory_over_sqlite3/secondary.conf
+        And wait for bind10 stderr message BIND10_STARTED_CC
+        And wait for bind10 stderr message CMDCTL_STARTED
         And wait for bind10 stderr message AUTH_SERVER_STARTED
         And wait for bind10 stderr message AUTH_SERVER_STARTED
         A query for www.example.org should have rcode NOERROR
         A query for www.example.org should have rcode NOERROR
         The SOA serial for example.org should be 1234
         The SOA serial for example.org should be 1234