features/cli.feature in modulesync-2.0.1 vs features/cli.feature in modulesync-2.0.2

@@ -2,34 +2,39 @@
   ModuleSync needs to have a robust command line interface
 
   Scenario: When passing no arguments to the msync command
     When I run `msync`
     And the output should match /Commands:/
+    Then the exit status should be 1
 
   Scenario: When passing invalid arguments to the msync update command
     When I run `msync update`
     And the output should match /No value provided for required option/
+    Then the exit status should be 1
 
   Scenario: When passing invalid arguments to the msync hook command
     When I run `msync hook`
     And the output should match /Commands:/
+    Then the exit status should be 1
 
-  Scenario: When running the help subcommand
+  Scenario: When running the help command
     When I run `msync help`
     And the output should match /Commands:/
+    Then the exit status should be 0
 
   Scenario: When overriding a setting from the config file on the command line
-    Given a file named "managed_modules.yml" with:
+    Given a puppet module "puppet-test" from "fakenamespace"
+    And a file named "managed_modules.yml" with:
       """
       ---
         - puppet-test
       """
     And a file named "modulesync.yml" with:
       """
       ---
-        namespace: maestrodev
-        git_base: '[e-mail]:'
+      namespace: default
       """
+    And a git_base option appended to "modulesync.yml" for local tests
     And a directory named "moduleroot"
-    When I run `msync update --noop --git-base https://github.com/`
+    When I run `msync update --noop --namespace fakenamespace`
     Then the exit status should be 0
-    And the output should not match /[e-mail]:/
+    And the output should match /Syncing fakenamespace/