Check E2E tests if an HTTP 404 / 500 returned
Description of the test
This is a test framework enhancement rather than a testcase.
Original issue - https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/997
If the page is found to be a 404, 500 or GDK backtrace, get the browser log and raise.
This prevents things like 'Cannot find element'
Checklist
-
N/A Confirm the test has a testcase:
tag linking to an existing test case in the test case project. -
N/A 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). -
N/A 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. -
N/A (If applicable) Create a follow-up issue to document the special setup necessary to run the test: ISSUE_LINK -
N/A 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 Will Meek