Last active
August 13, 2018 16:05
-
-
Save brgnepal/71d85cd9c3d52d98bd451ef053804ce0 to your computer and use it in GitHub Desktop.
Integration test results for Andy commits
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # Failed only two steps | |
| Feature: registry-route add-on | |
| registry-route add-on exposes the route for the OpenShift integrated registry, | |
| so that user can able to push their container images directly to registry and deploy it. | |
| The bash instance has been started and will be used for testing. | |
| Scenario: As a user, I can enable the registry-route add-on # features/addon-registry-route.feature:6 | |
| Given user starts shell instance on host machine # testsuite.go:778 -> /testsuite.startHostShellInstance | |
| When executing "minishift addons enable registry-route" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| Then stdout should contain "Add-on 'registry-route' enabled" # testsuite.go:555 -> /testsuite.commandReturnShouldContain | |
| Scenario: As a user, I can start Minishift with registry-route add-on enabled # features/addon-registry-route.feature:11 | |
| Given Minishift has state "Does Not Exist" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| And image caching is disabled # testsuite.go:92 -> *Minishift./testsuite.setImageCaching | |
| When executing "minishift start" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| Then Minishift should have state "Running" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| And stdout should contain # testsuite.go:563 -> /testsuite.commandReturnShouldContainContent | |
| """ | |
| Add-on 'registry-route' created docker-registry route. | |
| """ | |
| Scenario: As a user, I can login to OpenShift integrated docker registry # features/addon-registry-route.feature:21 | |
| Given Minishift has state "Running" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| And executing "minishift docker-env" in host shell succeeds # shell.go:286 -> /util.ExecuteMinishiftInHostShellSucceedsOrFails | |
| And evaluating stdout of the previous command in host shell # shell.go:268 -> /util.ExecuteInHostShellLineByLine | |
| And executing "minishift oc-env" in host shell succeeds # shell.go:286 -> /util.ExecuteMinishiftInHostShellSucceedsOrFails | |
| And evaluating stdout of the previous command in host shell # shell.go:268 -> /util.ExecuteInHostShellLineByLine | |
| ******************* Failed Step and later steps are skipped ***************** | |
| Then with up to "20" retries with wait period of "3" seconds container name "ose-docker-registry" should be "running" # testsuite.go:228 -> *Minishift./testsuite.containerStatus | |
| Container state did not match expected state within time limit of 60 seconds. Expected: running, Actual: | |
| And with up to "60" retries with wait period of "1" second command "curl -ik https://docker-registry-default.$(minishift ip).nip.io" output should contain "200 OK" # shell.go:291 -> /util.ExecuteCommandInHostShellWithRetry | |
| And executing "docker login -u developer -p `oc whoami -t` docker-registry-default.$(minishift ip).nip.io" in host shell succeeds # shell.go:236 -> /util.ExecuteInHostShellSucceedsOrFails | |
| And stdout of host shell should contain "Login Succeeded" # shell.go:295 -> /util.HostShellCommandReturnShouldContain | |
| Scenario: As a user, I can push pulled application image to OpenShift integrated docker registry and deploy it # features/addon-registry-route.feature:32 | |
| When executing "docker pull bitnami/nginx" in host shell succeeds # shell.go:236 -> /util.ExecuteInHostShellSucceedsOrFails | |
| Then executing "docker tag bitnami/nginx docker-registry-default.$(minishift ip).nip.io/myproject/nginx" in host shell succeeds # shell.go:236 -> /util.ExecuteInHostShellSucceedsOrFails | |
| ******************* Failed Step and later steps are skipped ***************** | |
| And executing "docker push docker-registry-default.$(minishift ip).nip.io/myproject/nginx" in host shell succeeds # shell.go:236 -> /util.ExecuteInHostShellSucceedsOrFails | |
| Command 'docker push docker-registry-default.$(minishift ip).nip.io/myproject/nginx', expected to succeed, exited with exit code: 1 | |
| And executing "oc get is" in host shell succeeds # shell.go:236 -> /util.ExecuteInHostShellSucceedsOrFails | |
| And stdout of host shell contains "nginx" # shell.go:295 -> /util.HostShellCommandReturnShouldContain | |
| And executing "oc new-app --image-stream=nginx --name=nginx" in host shell succeeds # shell.go:236 -> /util.ExecuteInHostShellSucceedsOrFails | |
| And stdout of host shell contains "Success" # shell.go:295 -> /util.HostShellCommandReturnShouldContain | |
| And executing "oc expose svc nginx" in host shell succeeds # shell.go:236 -> /util.ExecuteInHostShellSucceedsOrFails | |
| Then executing "oc set probe dc/nginx --readiness --get-url=http://:8080" in host shell succeeds # shell.go:236 -> /util.ExecuteInHostShellSucceedsOrFails | |
| And service "nginx" rollout successfully within "1200" seconds # testsuite.go:122 -> *Minishift./testsuite.rolloutServicesSuccessfullyBeforeTimeout | |
| And with up to "10" retries with wait period of "500ms" the "status code" of HTTP request to "/" of service "nginx" in namespace "myproject" is equal to "200" # testsuite.go:655 -> /testsuite.verifyRequestToServiceWithRetry | |
| And with up to "10" retries with wait period of "500ms" the "body" of HTTP request to "/" of service "nginx" in namespace "myproject" contains "Welcome to nginx!" # testsuite.go:655 -> /testsuite.verifyRequestToServiceWithRetry | |
| Scenario: As a user, I can login to OpenShift integrated docker registry after restart minishift # features/addon-registry-route.feature:46 | |
| Given Minishift has state "Running" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| When executing "minishift stop" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| Then executing "minishift start" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| And Minishift should have state "Running" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| And executing "minishift addon apply registry-route" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| Then with up to "60" retries with wait period of "3" seconds container name "registry_docker-registry" should be "running" # testsuite.go:228 -> *Minishift./testsuite.containerStatus | |
| And with up to "60" retries with wait period of "1" second command "curl -ik https://docker-registry-default.$(minishift ip).nip.io" output should contain "200 OK" # shell.go:291 -> /util.ExecuteCommandInHostShellWithRetry | |
| And executing "docker login -u developer -p `oc whoami -t` docker-registry-default.$(minishift ip).nip.io" in host shell succeeds # shell.go:236 -> /util.ExecuteInHostShellSucceedsOrFails | |
| And stdout of host shell should contain "Login Succeeded" # shell.go:295 -> /util.HostShellCommandReturnShouldContain | |
| Scenario: User deletes Minishift # features/addon-registry-route.feature:57 | |
| Given Minishift has state "Running" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| When executing "minishift delete --force" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| Then Minishift should have state "Does Not Exist" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| And user closes shell instance on host machine # shell.go:203 -> /util.CloseHostShellInstance | |
| Feature: xpaas add-on | |
| Xpaas add-on imports xPaaS templates and imagestreams, | |
| which are then available in OpenShift to the user. | |
| Feature: Basic | |
| As a user I can perform basic operations of Minishift and OpenShift | |
| Scenario: User can install default add-ons # features/basic.feature:5 | |
| When executing "minishift addons install --defaults" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| Then stdout should contain # testsuite.go:563 -> /testsuite.commandReturnShouldContainContent | |
| """ | |
| Default add-ons 'anyuid, admin-user, xpaas, registry-route, che, eap-cd' installed | |
| """ | |
| Scenario: User can enable the anyuid add-on # features/basic.feature:12 | |
| When executing "minishift addons enable anyuid" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| Then stdout should contain # testsuite.go:563 -> /testsuite.commandReturnShouldContainContent | |
| """ | |
| Add-on 'anyuid' enabled | |
| """ | |
| Scenario: Starting Minishift # features/basic.feature:24 | |
| Given Minishift has state "Does Not Exist" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| And image caching is disabled # testsuite.go:92 -> *Minishift./testsuite.setImageCaching | |
| When executing "minishift start" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| Then Minishift should have state "Running" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| When executing "minishift image list" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| Then stdout should be empty # testsuite.go:579 -> /testsuite.commandReturnShouldBeEmpty | |
| Scenario: OpenShift is ready after startup # features/basic.feature:32 | |
| Given Minishift has state "Running" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| When "status code" of HTTP request to "/healthz" of OpenShift instance is equal to "200" # testsuite.go:660 -> /testsuite.verifyRequestToOpenShift | |
| Then "body" of HTTP request to "/healthz" of OpenShift instance contains "ok" # testsuite.go:660 -> /testsuite.verifyRequestToOpenShift | |
| And "status code" of HTTP request to "/healthz/ready" of OpenShift instance is equal to "200" # testsuite.go:660 -> /testsuite.verifyRequestToOpenShift | |
| And "body" of HTTP request to "/healthz/ready" of OpenShift instance contains "ok" # testsuite.go:660 -> /testsuite.verifyRequestToOpenShift | |
| And "status code" of HTTP request to "/console" of OpenShift instance is equal to "200" # testsuite.go:660 -> /testsuite.verifyRequestToOpenShift | |
| And "body" of HTTP request to "/console" of OpenShift instance contains "<title>OpenShift Web Console</title>" # testsuite.go:660 -> /testsuite.verifyRequestToOpenShift | |
| Scenario Outline: User can set, get, view and unset values in configuration file # features/basic.feature:44 | |
| Given Minishift has state "Running" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| When executing "minishift config set <property> <value>" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| Then JSON config file ".minishift/config/config.json" contains key "<property>" with value matching "<value>" # testsuite.go:377 -> /testsuite.configFileContainsKeyMatchingValue | |
| And stdout of command "minishift config get <property>" is equal to "<value>" # testsuite.go:537 -> /testsuite.commandReturnEquals | |
| And stdout of command "minishift config view --format {{.ConfigKey}}:{{.ConfigValue}}" contains "<property>:<value>" # testsuite.go:546 -> /testsuite.commandReturnContains | |
| When executing "minishift config unset <property>" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| Then stdout of command "minishift config get <property>" is equal to "<nil>" # testsuite.go:537 -> /testsuite.commandReturnEquals | |
| And JSON config file ".minishift/config/config.json" does not have key "<property>" # testsuite.go:400 -> /testsuite.configFileContainsKey | |
| Examples: Config values to work with | |
| | property | value | | |
| | disk-size | 22g | | |
| | memory | 2222 | | |
| | cpus | 3 | | |
| Scenario: User can get IP of provided virtual machine # features/basic.feature:64 | |
| Given Minishift has state "Running" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| When executing "minishift ip" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| Then stdout should be valid IP # testsuite.go:475 -> /testsuite.shouldBeInValidFormat | |
| Scenario: User can get URL of OpenShift console # features/basic.feature:71 | |
| Given Minishift has state "Running" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| When executing "minishift console --url" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| Then stdout should be valid URL # testsuite.go:475 -> /testsuite.shouldBeInValidFormat | |
| When executing "minishift dashboard --url" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| Then stdout should be valid URL # testsuite.go:475 -> /testsuite.shouldBeInValidFormat | |
| Scenario: OpenShift developer has sudo permissions # features/basic.feature:79 | |
| Given Minishift has state "Running" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| When executing "oc --as system:admin get clusterrolebindings" succeeds # testsuite.go:609 -> /testsuite.ExecutingOcCommandSucceedsOrFails | |
| Then stdout should contain # testsuite.go:563 -> /testsuite.commandReturnShouldContainContent | |
| """ | |
| sudoer | |
| """ | |
| Scenario: Sudo permissions are required for specific oc tasks # features/basic.feature:89 | |
| Given Minishift has state "Running" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| Then executing "oc get clusterrolebindings" fails # testsuite.go:609 -> /testsuite.ExecutingOcCommandSucceedsOrFails | |
| Scenario: A 'minishift' context is created for 'oc' usage # features/basic.feature:93 | |
| Given Minishift has state "Running" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| When executing "oc config current-context" succeeds # testsuite.go:609 -> /testsuite.ExecutingOcCommandSucceedsOrFails | |
| Then stdout should contain # testsuite.go:563 -> /testsuite.commandReturnShouldContainContent | |
| """ | |
| minishift | |
| """ | |
| Scenario: User can switch the current 'oc' context and return to 'minishift' context # features/basic.feature:103 | |
| Given executing "oc config set-context dummy" succeeds # testsuite.go:609 -> /testsuite.ExecutingOcCommandSucceedsOrFails | |
| And executing "oc config use-context dummy" succeeds # testsuite.go:609 -> /testsuite.ExecutingOcCommandSucceedsOrFails | |
| When executing "oc project -q" # minishift.go:187 -> *Minishift | |
| Then exitcode should equal "1" # testsuite.go:571 -> /testsuite.commandReturnShouldEqual | |
| When executing "oc config use-context minishift" succeeds # testsuite.go:609 -> /testsuite.ExecutingOcCommandSucceedsOrFails | |
| And executing "oc config current-context" succeeds # testsuite.go:609 -> /testsuite.ExecutingOcCommandSucceedsOrFails | |
| Then stdout should contain # testsuite.go:563 -> /testsuite.commandReturnShouldContainContent | |
| """ | |
| minishift | |
| """ | |
| Scenario: User has a pre-configured set of persistent volumes # features/basic.feature:115 | |
| When executing "oc --as system:admin get pv -o=name" # minishift.go:187 -> *Minishift | |
| Then stderr should be empty # testsuite.go:579 -> /testsuite.commandReturnShouldBeEmpty | |
| And exitcode should equal "0" # testsuite.go:571 -> /testsuite.commandReturnShouldEqual | |
| And stdout should contain # testsuite.go:563 -> /testsuite.commandReturnShouldContainContent | |
| """ | |
| persistentvolumes/pv0001 | |
| """ | |
| Scenario: User is able to do ssh into Minishift VM # features/basic.feature:124 | |
| Given Minishift has state "Running" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| When executing "minishift ssh echo hello" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| Then stdout should contain # testsuite.go:563 -> /testsuite.commandReturnShouldContainContent | |
| """ | |
| hello | |
| """ | |
| Scenario: User is able to retrieve host and port of OpenShift registry # features/basic.feature:132 | |
| Given Minishift has state "Running" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| When executing "minishift openshift registry" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| Then stdout should contain # testsuite.go:563 -> /testsuite.commandReturnShouldContainContent | |
| """ | |
| 172.30.1.1:5000 | |
| """ | |
| Scenario: User can deploy a Ruby example application # features/basic.feature:140 | |
| Given Minishift has state "Running" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| When executing "oc login --username=developer --password=developer" succeeds # testsuite.go:609 -> /testsuite.ExecutingOcCommandSucceedsOrFails | |
| And executing "oc new-project ruby" succeeds # testsuite.go:609 -> /testsuite.ExecutingOcCommandSucceedsOrFails | |
| And executing "oc new-app centos/ruby-22-centos7~https://github.com/openshift/ruby-ex.git" succeeds # testsuite.go:609 -> /testsuite.ExecutingOcCommandSucceedsOrFails | |
| And executing "oc expose svc/ruby-ex" succeeds # testsuite.go:609 -> /testsuite.ExecutingOcCommandSucceedsOrFails | |
| And executing "oc set probe dc/ruby-ex --readiness --get-url=http://:8080" succeeds # testsuite.go:609 -> /testsuite.ExecutingOcCommandSucceedsOrFails | |
| And service "ruby-ex" rollout successfully within "1200" seconds # testsuite.go:122 -> *Minishift./testsuite.rolloutServicesSuccessfullyBeforeTimeout | |
| Then with up to "10" retries with wait period of "500ms" the "status code" of HTTP request to "/" of service "ruby-ex" in namespace "ruby" is equal to "200" # testsuite.go:655 -> /testsuite.verifyRequestToServiceWithRetry | |
| And with up to "10" retries with wait period of "500ms" the "body" of HTTP request to "/" of service "ruby-ex" in namespace "ruby" contains "Welcome to your Ruby application on OpenShift" # testsuite.go:655 -> /testsuite.verifyRequestToServiceWithRetry | |
| When executing "oc delete project ruby" succeeds # testsuite.go:609 -> /testsuite.ExecutingOcCommandSucceedsOrFails | |
| Then stdout should contain "project "ruby" deleted" # testsuite.go:555 -> /testsuite.commandReturnShouldContain | |
| When executing "oc logout" succeeds # testsuite.go:609 -> /testsuite.ExecutingOcCommandSucceedsOrFails | |
| Then stdout should contain # testsuite.go:563 -> /testsuite.commandReturnShouldContainContent | |
| """ | |
| Logged "developer" out | |
| """ | |
| Scenario: As a user I am able to export a container image from a running Minshift instance # features/basic.feature:161 | |
| When executing "minishift image export alpine:latest" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| Then stdout of command "minishift image list" contains "alpine:latest" # testsuite.go:546 -> /testsuite.commandReturnContains | |
| Scenario: Stopping Minishift # features/basic.feature:167 | |
| Given Minishift has state "Running" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| When executing "minishift stop" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| Then Minishift should have state "Stopped" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| When executing "minishift stop" # minishift.go:191 -> *Minishift | |
| Then Minishift should have state "Stopped" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| And stdout should contain # testsuite.go:563 -> /testsuite.commandReturnShouldContainContent | |
| """ | |
| The 'minishift' VM is already stopped. | |
| """ | |
| When executing "minishift console" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| Then stdout should contain # testsuite.go:563 -> /testsuite.commandReturnShouldContainContent | |
| """ | |
| Running this command requires a running 'minishift' VM, but no VM is running. | |
| """ | |
| When executing "minishift ip" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| Then stdout should contain # testsuite.go:563 -> /testsuite.commandReturnShouldContainContent | |
| """ | |
| Running this command requires a running 'minishift' VM, but no VM is running. | |
| """ | |
| Scenario: Deleting Minishift # features/basic.feature:189 | |
| Given Minishift has state "Stopped" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| When executing "minishift delete --force --clear-cache" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| Then Minishift should have state "Does Not Exist" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| Scenario: Provision non-default OpenShift version # features/basic.feature:194 | |
| Given Minishift has state "Does Not Exist" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| And image caching is disabled # testsuite.go:92 -> *Minishift./testsuite.setImageCaching | |
| When executing "minishift start --ocp-tag v3.7.23" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| Then Minishift should have state "Running" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| When executing "minishift openshift version" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| Then stdout should contain # testsuite.go:563 -> /testsuite.commandReturnShouldContainContent | |
| """ | |
| openshift v3.7.23 | |
| """ | |
| And JSON config file ".minishift/machines/minishift-state.json" contains key "OcPath" with value matching "v3.7.23" # testsuite.go:377 -> /testsuite.configFileContainsKeyMatchingValue | |
| When executing "minishift oc-env" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| Then stdout should contain # testsuite.go:563 -> /testsuite.commandReturnShouldContainContent | |
| """ | |
| v3.7.23 | |
| """ | |
| And "status code" of HTTP request to "/healthz" of OpenShift instance is equal to "200" # testsuite.go:660 -> /testsuite.verifyRequestToOpenShift | |
| And "body" of HTTP request to "/healthz" of OpenShift instance contains "ok" # testsuite.go:660 -> /testsuite.verifyRequestToOpenShift | |
| And "status code" of HTTP request to "/healthz/ready" of OpenShift instance is equal to "200" # testsuite.go:660 -> /testsuite.verifyRequestToOpenShift | |
| And "body" of HTTP request to "/healthz/ready" of OpenShift instance contains "ok" # testsuite.go:660 -> /testsuite.verifyRequestToOpenShift | |
| And "status code" of HTTP request to "/console" of OpenShift instance is equal to "200" # testsuite.go:660 -> /testsuite.verifyRequestToOpenShift | |
| And "body" of HTTP request to "/console" of OpenShift instance contains "<title>OpenShift Web Console</title>" # testsuite.go:660 -> /testsuite.verifyRequestToOpenShift | |
| When executing "minishift delete --force" succeeds # testsuite.go:613 -> /testsuite.ExecutingMinishiftCommandSucceedsOrFails | |
| Then Minishift should have state "Does Not Exist" # testsuite.go:77 -> *Minishift./testsuite.shouldHaveState | |
| Feature: Addons command and its subcommands | |
| Feature: Minishift config subcommands | |
| Commands `minishift config [sub-command]` are used for storing | |
| user defined options which changes default behaviour of Minishift. | |
| Feature: Command docker-env | |
| Command docker-env sets docker environment variables for supported shells. | |
| INFO: This feature runs against a shell instance. To use a non-default shell, please select | |
| one from: bash, cmd, powershell, tcsh, zsh with TEST_WITH_SPECIFIED_SHELL parameter of make integration. | |
| Feature: Basic image caching test | |
| As a user I am able to import and export container images from a local OCI repository | |
| located in the $MINISHIFT_HOME/cache directory | |
| Feature: Command oc-env | |
| Command oc-env sets the path to oc binary. | |
| INFO: This feature runs against a shell instance. To use a non-default shell, please select | |
| one from: bash, cmd, powershell, tcsh, zsh with TEST_WITH_SPECIFIED_SHELL parameter of make integration. | |
| Feature: Openshift commands | |
| Commands "minishift openshift [sub-command]" are used for interaction with Openshift | |
| cluster in VM provided by Minishift. | |
| Feature: Profile commands | |
| As a user I can perform basic operations of Minishift with profile feature | |
| Feature: Version command | |
| Command "minishift version" shows version of minishift binary. | |
| Feature: Cool Store | |
| In order to test Minishift under load | |
| I need to setup a test environment | |
| Using CentOS and 4G of memory | |
| After which I will import image streams | |
| Finally I will deploy the Cool Store | |
| Feature: Experimental Flags | |
| Experimental flag --extra-clusterup-flags will be enabled by setting MINISHIFT_ENABLE_EXPERIMENTAL environment variable, | |
| this flag will provide access to some of upcoming feature and experiments. | |
| Feature: Flags | |
| As a user I can perform advanced operations | |
| such as starting Minishift with optional features | |
| Feature: With generic driver Minishift can provision remote unprovisioned VM | |
| Feature: Provision all major OpenShift versions | |
| As a user I can provision major versions of OpenShift | |
| Feature: Minishift can run behind proxy | |
| As a user I can use Minishift behind a proxy. | |
| INFO: Code behind this feature will start a proxy server in background | |
| on port 8181 and will try to get IP of host machine automatically | |
| to set MINISHIFT_HTTP_PROXY for this feature only. | |
| However one can override port number or set IP manually if needed. | |
| To use custom port number run this test with environmental variable | |
| INTEGRATION_PROXY_CUSTOM_PORT. | |
| To use custom IP address please set INTEGRATION_PROXY_CUSTOM_IP | |
| environmental variable. | |
| Feature: Setup CDK | |
| As a user I can able to setup CDK | |
| --- Failed steps: | |
| Scenario: As a user, I can login to OpenShift integrated docker registry # features/addon-registry-route.feature:21 | |
| Then with up to "20" retries with wait period of "3" seconds container name "ose-docker-registry" should be "running" # features/addon-registry-route.feature:27 | |
| Error: Container state did not match expected state within time limit of 60 seconds. Expected: running, Actual: | |
| Scenario: As a user, I can push pulled application image to OpenShift integrated docker registry and deploy it # features/addon-registry-route.feature:32 | |
| And executing "docker push docker-registry-default.$(minishift ip).nip.io/myproject/nginx" in host shell succeeds # features/addon-registry-route.feature:35 | |
| Error: Command 'docker push docker-registry-default.$(minishift ip).nip.io/myproject/nginx', expected to succeed, exited with exit code: 1 | |
| 32 scenarios (30 passed, 2 failed) | |
| 179 steps (165 passed, 2 failed, 12 skipped) | |
| 44m50.348649898s | |
| testing: warning: no tests to run |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment