Skip to content

E2E for Content Editor in Wiki

Anastasia McDonald requested to merge qa-e2e-content-editor-spec into master

Description of the test

Add a new E2E to test the following end-to-end user scenario that cannot be covered by unit/system tests:

  • Click 'New Page' in Wiki -> Choose to use the new editor -> Add basic formatting & upload an image -> Save & Verify

Content Editor is currently being trialled in Wiki but will be eventually rolled out Gitlab-wide. We should start building up test coverage as the feature being developed. See &5401

Testcase issue: gitlab-org/quality/testcases#1861 (closed)

Check-list

  • 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 under gitlab-qa-sandbox-group.
  • Ensure that no transient bugs are hidden accidentally due to the usage of waits and reloads.
  • 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 with and without the GITLAB_QA_ADMIN_ACCESS_TOKEN provided.
Edited by Anastasia McDonald

Merge request reports