Failure in qa/specs/features/browser_ui/4_verify/ci_variable/add_remove_ci_variable_spec on Staging - expected not to find text "VARIABLE_KEY"
Summary
Failure in qa/specs/features/browser_ui/4_verify/ci_variable/add_remove_ci_variable_spec
expected not to find text "VARIABLE_KEY"
Seen on staging - https://ops.gitlab.net/gitlab-org/gitlab-qa/-/jobs/1795346
Looks similar to old closed issue #217438 (closed)
Stack trace
Test:
D, [2020-09-08T13:01:57.603918 #23] DEBUG -- : clicking :ci_variable_delete_button with args {}
D, [2020-09-08T13:01:57.666759 #23] DEBUG -- : waiting for loading to complete...
D, [2020-09-08T13:01:57.666875 #23] DEBUG -- : with retry_on_exception: max_attempts: 3; reload_page: ; sleep_interval: 0.5
D, [2020-09-08T13:01:57.667230 #23] DEBUG -- : Attempt number 1
D, [2020-09-08T13:01:57.688501 #23] DEBUG -- : ended retry_on_exception
D, [2020-09-08T13:01:57.688599 #23] DEBUG -- : loading complete after 0.021739321 seconds
[31m user removes a CI variable (FAILED - 1)[0m
1st Try error in ./qa/specs/features/browser_ui/4_verify/ci_variable/add_remove_ci_variable_spec.rb:32:
expected not to find text "VARIABLE_KEY" in "Variables Collapse Environment variables are applied to environments via the Runner. You can use environment variables for passwords, secret keys, etc. Make variables available to the running application by prepending the variable key with K8S_SECRET_. You can set variables to be: Protected variables are only exposed to protected branches or tags. Masked variables are hidden in job logs (though they must match certain regexp requirements to do so). More information Environment variables are configured by your administrator to be protected by default Type Key (Click to sort Descending) Value Protected Masked Environments Variable VARIABLE_KEY ********************* All (default) Reveal values Add Variable Group variables (inherited) These variables are configured in the parent group settings, and will be active in the current project in addition to the project variables. Key Origin"
1) Verify Add or Remove CI variable via UI user removes a CI variable
Failure/Error: expect(page).not_to have_text('VARIABLE_KEY')
expected not to find text "VARIABLE_KEY" in "Variables Collapse Environment variables are applied to environments via the Runner. You can use environment variables for passwords, secret keys, etc. Make variables available to the running application by prepending the variable key with K8S_SECRET_. You can set variables to be: Protected variables are only exposed to protected branches or tags. Masked variables are hidden in job logs (though they must match certain regexp requirements to do so). More information Environment variables are configured by your administrator to be protected by default Type Key (Click to sort Descending) Value Protected Masked Environments Variable VARIABLE_KEY ********************* All (default) Reveal values Add Variable Group variables (inherited) These variables are configured in the parent group settings, and will be active in the current project in addition to the project variables. Key Origin"
# ./qa/specs/features/browser_ui/4_verify/ci_variable/add_remove_ci_variable_spec.rb:38:in `block (5 levels) in <module:QA>'
# ./qa/scenario/actable.rb:16:in `perform'
# ./qa/page/project/settings/ci_cd.rb:31:in `block in expand_ci_variables'
# ./qa/page/settings/common.rb:19:in `block in expand_content'
# ./qa/page/base.rb:272:in `block in within_element'
# /usr/local/bundle/gems/capybara-3.29.0/lib/capybara/session.rb:343:in `within'
# ./qa/page/base.rb:271:in `within_element'
# ./qa/support/page/logging.rb:149:in `within_element'
# ./qa/page/settings/common.rb:11:in `expand_content'
# ./qa/page/project/settings/ci_cd.rb:30:in `expand_ci_variables'
# ./qa/specs/features/browser_ui/4_verify/ci_variable/add_remove_ci_variable_spec.rb:34:in `block (4 levels) in <module:QA>'
# ./qa/scenario/actable.rb:16:in `perform'
# ./qa/specs/features/browser_ui/4_verify/ci_variable/add_remove_ci_variable_spec.rb:33:in `block (3 levels) in <module:QA>'
# /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:123:in `block in run'
# /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:110:in `loop'
# /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:110:in `run'
# /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec_ext/rspec_ext.rb:12:in `run_with_retry'
# ./spec/spec_helper.rb:70:in `block (2 levels) in <top (required)>'
# /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:123:in `block in run'
# /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:110:in `loop'
# /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:110:in `run'
# /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec_ext/rspec_ext.rb:12:in `run_with_retry'
# /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:37:in `block (2 levels) in setup'
# ./qa/specs/runner.rb:71:in `perform'
# ./qa/scenario/template.rb:10:in `block in perform'
# ./qa/scenario/template.rb:8:in `tap'
# ./qa/scenario/template.rb:8:in `perform'
# ./qa/scenario/template.rb:35:in `perform'
# ./qa/scenario/template.rb:10:in `block in perform'
# ./qa/scenario/template.rb:8:in `tap'
# ./qa/scenario/template.rb:8:in `perform'
# ./qa/scenario/bootable.rb:28:in `launch!'
Screenshot / HTML page
verify_add_or_remove_ci_variable_via_ui_user_removes_a_ci_variable.html