Run e2e test of code suggestions on Staging too
What does this MR do and why?
Run the code suggestions e2e tests on staging too
Test results
Run from my machine against gitlab.com
I cut most of the log messages so it just shows the test ran successfully
==> Base URL: https://gitlab.com
ModelOps
Code Suggestions
on the GitLab API with PAT auth
returns a suggestion
Top 1 slowest examples (0.9429 seconds, 99.3% of total time):
ModelOps Code Suggestions on the GitLab API with PAT auth returns a suggestion
0.9429 seconds ./qa/specs/features/ee/api/14_model_ops/code_suggestions_spec.rb:55
Finished in 0.94907 seconds (files took 3.66 seconds to load)
1 example, 0 failures
Run from my machine against staging.gitlab.com
I cut most of the log messages so it just shows the test ran successfully
==> Base URL: https://staging.gitlab.com
ModelOps
Code Suggestions
on the GitLab API with PAT auth
returns a suggestion
Top 1 slowest examples (1.78 seconds, 99.5% of total time):
ModelOps Code Suggestions on the GitLab API with PAT auth returns a suggestion
1.78 seconds ./qa/specs/features/ee/api/14_model_ops/code_suggestions_spec.rb:55
Finished in 1.79 seconds (files took 3.44 seconds to load)
1 example, 0 failures
How to set up and validate locally
You can run the tests against staging.gitlab.com using the gitlab-qa
user as the tests do, or by using your own user. If you use gitlab-qa
you can skip below to running the tests, otherwise enable the Code Suggestions user preference (see https://docs.gitlab.com/ee/user/project/repository/code_suggestions.html#enable-code-suggestions-for-an-individual-user)
To run the tests, from the qa
directory:
export GITLAB_USERNAME=gitlab-qa # or your own username if you have Code Suggestions enabled in your preferences and via the feature flag
export GITLAB_QA_ACCESS_TOKEN=<from 1Password> # or your own access token
bundle install
bundle exec bin/qa Test::Instance::All https://staging.gitlab.com https://gitlab.com qa/specs/features/ee/api/14_model_ops/code_suggestions_spec.rb
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Mark Lapierre