test (e2e) : add e2e test for developer-password config option

+ Add additional assertions in basic test to verify that when no developer password is configured,
  then "developer" value is used for password
+ Add custom_developer_password e2e test to verify that when custom developer-password configuration
  option is provided, then that custom value is used as developer password

Signed-off-by: Rohan Kumar <[email protected]>

Author: rohanKanojia

test/e2e/features/basic.feature

@@ -31,13 +31,19 @@ Feature: Basic test
     @darwin @linux @windows @cleanup
     Scenario: CRC start usecase
         Given executing "crc setup --check-only" fails
+        And unsetting config property "developer-password" succeeds
         # Request start with monitoring stack
         * setting config property "enable-cluster-monitoring" to value "true" succeeds
         * setting config property "memory" to value "16000" succeeds
         Given executing single crc setup command succeeds
         And executing "man -P cat crc" succeeds
         When starting CRC with default bundle succeeds
         Then stdout should contain "Started the OpenShift cluster"
+        And stdout should contain "Log in as administrator:"
+        And stdout should contain "  Username: kubeadmin"
+        And stdout should contain "Log in as user:"
+        And stdout should contain "  Username: developer"
+        And stdout should contain "  Password: developer"
         # Check if user can copy-paste login details for developer and kubeadmin users
         * stdout should match "(?s)(.*)oc login -u developer https:\/\/api\.crc\.testing:6443(.*)$"
         * stdout should match "(?s)(.*)https:\/\/console-openshift-console\.apps-crc\.testing(.*)$"

test/e2e/features/config.feature

@@ -17,27 +17,30 @@ Feature: Test configuration settings
         # always return to default values
         @darwin
         Examples: Config settings on Mac
-            | property         | value1    | value2            |
-            | cpus             | 5         | 3                 |
-            | memory           | 10753     | 4096              |
-            | nameserver       | 120.0.0.1 | 999.999.999.999   |
-            | pull-secret-file | /etc      | /nonexistent-file |
+            | property           | value1    | value2            |
+            | cpus               | 5         | 3                 |
+            | memory             | 10753     | 4096              |
+            | nameserver         | 120.0.0.1 | 999.999.999.999   |
+            | pull-secret-file   | /etc      | /nonexistent-file |
+            | developer-password | secret1   |                   |
 
         @linux
         Examples: Config settings on Linux
-            | property         | value1    | value2            |
-            | cpus             | 5         | 3                 |
-            | memory           | 10753     | 4096              |
-            | nameserver       | 120.0.0.1 | 999.999.999.999   |
-            | pull-secret-file | /etc      | /nonexistent-file |
+            | property           | value1    | value2            |
+            | cpus               | 5         | 3                 |
+            | memory             | 10753     | 4096              |
+            | nameserver         | 120.0.0.1 | 999.999.999.999   |
+            | pull-secret-file   | /etc      | /nonexistent-file |
+            | developer-password | secret1   |                   |
 
         @windows
         Examples: Config settings on Windows
-            | property         | value1    | value2            |
-            | cpus             | 5         | 3                 |
-            | memory           | 10753     | 4096              |
-            | nameserver       | 120.0.0.1 | 999.999.999.999   |
-            | pull-secret-file | /Users    | /nonexistent-file |
+            | property           | value1    | value2            |
+            | cpus               | 5         | 3                 |
+            | memory             | 10753     | 4096              |
+            | nameserver         | 120.0.0.1 | 999.999.999.999   |
+            | pull-secret-file   | /Users    | /nonexistent-file |
+            | developer-password | secret1   |                   |
 
     @linux @darwin @windows
     Scenario: CRC config checks (bundle version)
@@ -171,14 +174,14 @@ Feature: Test configuration settings
         When unsetting config property "preset" succeeds
         And stdout should contain "Successfully unset configuration property 'preset'"
         And "JSON" config file "crc.json" in CRC home folder does not contain key "preset"
-        
-        @linux @darwin @windows 
+
+    @linux @darwin @windows
         Examples: Config property preset setting positive
             | preset-value  |
             | microshift    | 
             | okd           | 
 
-    Scenario: CRC config set preset (negtive cases) 
+    Scenario: CRC config set preset (negative cases)
         When setting config property "preset" to value "<preset-value>" fails
         And stderr should contain "reason: Unknown preset" 
 

test/e2e/features/custom_developer_password.feature

@@ -0,0 +1,19 @@
+@story_custom_developer_password
+Feature: Custom Developer Password Test
+
+    User provides configuration property to override default developer user password
+
+    Background:
+        Given ensuring CRC cluster is running
+
+    @linux @windows @darwin @cleanup
+    Scenario: Override default developer password should be reflected during crc start
+        Given executing "crc stop" succeeds
+        And setting config property "developer-password" to value "secret-dev" succeeds
+        When starting CRC with default bundle succeeds
+        Then stdout should contain "Started the OpenShift cluster"
+        And stdout should contain "Log in as administrator:"
+        And stdout should contain "  Username: kubeadmin"
+        And stdout should contain "Log in as user:"
+        And stdout should contain "  Username: developer"
+        And stdout should contain "  Password: secret-dev"