Format go and more robust tests

Compose in tests adds suffix to containers

CHANGELOG.md

@@ -51,6 +51,7 @@ Are you ready to get STABLE!
 - Reversed changelog output, newest changes are at the bottom
 - `dab config keys` can now take a config key to limit its output
 - Moved some hooks to post execution such as checking wrapper updates
+- More robust tests
 
 ### Added
 

completion/main.go

@@ -114,7 +114,7 @@ var dab = complete.Command{
 			},
 		},
 		"shell": {}, "sh": {}, "cmd": {},
-		"tip": {},
+		"tip":    {},
 		"update": {}, "upgrade": {},
 		"changelog": {}, "changes": {},
 	},

tests/features/group.feature

@@ -60,7 +60,8 @@ Feature: Subcommand: dab group
 		"""
 		Executing six entrypoint start
 		"""
-		And I successfully run `docker top services_redis_1`
+		And I successfully run `docker ps`
+		And output should contain "services_redis_1"
 
 	Scenario: Can group groups and repos then start them together
 		Given I successfully run `dab services stop`
@@ -78,4 +79,5 @@ Feature: Subcommand: dab group
 		"""
 		Executing seven entrypoint deploy
 		"""
-		And I successfully run `docker top services_redis_1`
+		And I successfully run `docker ps`
+		And output should contain "services_redis_1"

tests/features/services.feature

@@ -23,15 +23,15 @@ Feature: Subcommand: dab services
 		And the output should contain "Building"
 
 	Scenario Outline: Can start and stop services
-		When I run `dab services start <SERVICE>`
+		When I successfully run `dab services start <SERVICE>`
 
-		Then the exit status should be 0
-		And I successfully run `docker top services_<SERVICE>_1`
+		Then I successfully run `docker ps`
+		And output should contain "services_<SERVICE>_1"
 
 		When I successfully run `dab services stop <SERVICE>`
 
-		Then I run `docker top services_<SERVICE>_1`
-		And it should fail with "is not running"
+		Then I successfully run `docker ps`
+		And output should contain not "services_<SERVICE>_1"
 
 		Examples:
 			| SERVICE   |
@@ -67,13 +67,13 @@ Feature: Subcommand: dab services
 
 		When I run `dab services stop`
 
-		Then I run `docker top services_redis_1`
-		And it should fail with "is not running"
+		Then I successfully run `docker ps`
+		And output should contain not "services_redis_1"
 
 	Scenario: Can erase all services and their state at once
 		Given I successfully run `dab services start redis`
 
 		When I run `dab services destroy`
 
-		Then I run `docker top services_redis_1`
-		And it should fail with "No such container"
+		Then I successfully run `docker ps`
+		And output should contain not "services_redis_1"

tests/features/tools.feature

@@ -29,12 +29,13 @@ Feature: Subcommand: dab tools
 		"""
 		^<TOOL> is available at https?://localhost:[0-9]+$
 		"""
-		And I successfully run `docker top tools_<TOOL>_1`
+		And I successfully run `docker ps`
+		And output should contain "tools_<TOOL>_1"
 
 		When I successfully run `dab tools stop <TOOL>`
 
-		Then I run `docker top tools_<TOOL>_1`
-		And it should fail with "is not running"
+		Then I successfully run `docker ps`
+		And output should contain not "tools_<TOOL>_1"
 
 		Examples:
 			| TOOL       |
@@ -71,14 +72,14 @@ Feature: Subcommand: dab tools
 
 		When I run `dab tools stop`
 
-		Then I run `docker top tools_cyberchef_1`
-		And it should fail with "is not running"
+		Then I successfully run `docker ps`
+		And output should contain not "tools_cyberchef_1"
 
 	Scenario: Can erase all tools and their state at once
 		Given I successfully run `dab tools start cyberchef`
 
 		When I run `dab tools destroy`
 		And it should pass with "Stopping tools_cyberchef_1 ... done"
 
-		Then I run `docker top tools_cyberchef_1`
-		And it should fail with "No such container"
+		Then I successfully run `docker ps`
+		And output should contain not "tools_cyberchef_1"