Maintenance tests now live in their own feature

tests/integration/features/bootstrap/CommandLineContext.php

@@ -123,7 +123,7 @@ public function maintenanceModeIs($state) {
 	}
 
 	/**
-	 * @AfterScenario
+	 * @AfterScenario @maintenance_mode
 	 *
 	 * Disables maintenance mode in case it was enabled.
 	 */

tests/integration/features/maintenance-mode.feature

@@ -0,0 +1,16 @@
+Feature: maintenance-mode
+	Background:
+		Given using api version "1"
+		And maintenance mode is enabled
+
+	@maintenance_mode
+	Scenario: Maintenance mode new dav path
+		Given using new dav path
+		When Connecting to dav endpoint as user "admin"
+ 		Then the HTTP status code should be "503"
+
+ 	@maintenance_mode
+	Scenario: Maintenance mode old dav path
+		Given using old dav path
+		When Connecting to dav endpoint as user "admin"
+ 		Then the HTTP status code should be "503"

tests/integration/features/webdav-related-new-endpoint.feature

@@ -543,10 +543,3 @@ Feature: webdav-related-new-endpoint
 		And user "user0" uploads new chunk file "3" with "CCCCC" to id "chunking-42"
 		When user "user0" moves new chunk file with id "chunking-42" to "/existingFile.txt"
 		Then User "user0" checks id of file "/existingFile.txt"
-
-	Scenario: Maintenance mode
-		Given using new dav path
-		And maintenance mode is enabled
-		When Connecting to dav endpoint as user "admin"
- 		Then the HTTP status code should be "503"
-

tests/integration/features/webdav-related-old-endpoint.feature

@@ -487,8 +487,3 @@ Feature: webdav-related-old-endpoint
 		And Downloading file "/myChunkedFile.txt"
 		Then Downloaded content should be "AAAAABBBBBCCCCC"
 
-	Scenario: Maintenance mode
-		Given maintenance mode is enabled
-		When Connecting to dav endpoint as user "admin"
- 		Then the HTTP status code should be "503"
-