Skip to content

Test failures / flakiness - investigate tooling to read a screenshot and identify a 502 or similar error

Goal

Change the description of an issue to tell if it's 502

Problem statement

Occasionally we may see failures such as

https://gitlab.com/gitlab-org/quality/e2e-test-issues/-/issues/188

where the failure is reported as

  Unable to find css "[data-testid=\"protected-tag-settings-content\"]"

However on observing the screenshot we can see a 502 error message.

We might want to investigate tooling that could parse the screenshot and identify it as a 502 error (or other errors) and report as such.

Alternatively we might want to look at extending https://gitlab.com/gitlab-org/gitlab/blob/master/qa/qa/support/page_error_checker.rb , and have it parse for 502s.

Please benchmark it against test speed.

Status

Edited by Nadya Denisenko