test: crc should stop without force otherwise it is a bug

crc-org · Jul 23, 2021 · 5ca59b8 · 5ca59b8
1 parent 171f906
commit 5ca59b8
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/test/e2e/features/basic.feature b/test/e2e/features/basic.feature
@@ -151,8 +151,8 @@ Feature: Basic test
         Given executing "crc bundle generate -f" succeeds
 
     @darwin @windows
-    Scenario: CRC forcible stop
-        When executing "crc stop -f"
+    Scenario: CRC stop
+        When executing "crc stop"
         Then stdout should match "(.*)[Ss]topped the OpenShift cluster"
         And executing "oc whoami" fails
 

diff --git a/test/e2e/features/story_health.feature b/test/e2e/features/story_health.feature
@@ -49,7 +49,7 @@ Feature: End-to-end health check
     @darwin @linux @windows
     Scenario: Stop and start CRC, then check app still runs
         Given with up to "2" retries with wait period of "60s" http response from "http://httpd-example-testproj.apps-crc.testing" has status code "200"
-        When executing "crc stop -f" succeeds
+        When executing "crc stop" succeeds
         Then checking that CRC is stopped
         When starting CRC with default bundle succeeds
         Then checking that CRC is running