E2E - pipeline editor lint
Description of the test
New E2E test for pipeline editor linting capability.
- Testcase 1 https://gitlab.com/gitlab-org/gitlab/-/quality/test_cases/349128 - when CI has valid syntax
- There is valid syntax message on editor page
- Visualize tab shows jobs defined in CI file
- Lint tab status shows syntax is correct
- View merged YAML tab shows source editor
- Testcase 2 https://gitlab.com/gitlab-org/gitlab/-/quality/test_cases/349129 - when CI has invalid syntax
- There is invalid syntax message on editor page
- Visualize tab show syntax invalid alert
- Lint tab status shows syntax is incorrect alert
- View merged YAML tab shows syntax invalid alert
Checklist
-
Confirm the test has a testcase:
tag linking to an existing test case in the test case project. -
Note if the test is intended to run in specific scenarios. If a scenario is new, add a link to the MR that adds the new scenario. -
Follow the end-to-end tests style guide and best practices. -
Use the appropriate RSpec metadata tag(s). -
Ensure that a created resource is removed after test execution. A Group
resource can be shared between multiple tests. Do not remove it unless it has a unique path. Note that we have a cleanup job that periodically removes groups undergitlab-qa-sandbox-group
. -
Ensure that no transient bugs are hidden accidentally due to the usage of waits
andreloads
. -
Verify the tags to ensure it runs on the desired test environments. -
If this MR has a dependency on another MR, such as a GitLab QA MR, specify the order in which the MRs should be merged. -
(If applicable) Create a follow-up issue to document the special setup necessary to run the test: ISSUE_LINK -
If the test requires an admin's personal access token, ensure that the test passes on your local environment with and without the GITLAB_QA_ADMIN_ACCESS_TOKEN
provided.
Edited by Tiffany Rea