If a 3.x E2E test fails, the relevant GitHub action will fail with an error message. Most of the time the error messages are too generic (ex: “Couldn’t find element X ”) and hard to get an idea of. To identify the issue, the developers must obtain a clone of the QA framework and run the specific test locally using Cypress Runner. Business-type stakeholders require the assistance of developers to identify the actual problem. Moreover, there might be some rare scenarios that are hard to reproduce locally. Especially, the current setup sometimes throws random errors.
Cypress has an inbuilt screen recording feature. So that we could record the screen and attach the recordings of failed tests to the GitHub workflow. With that, anyone can check failing workflow in the QA dashboard and play the attached screen recording without running them locally. It saves a lot of time and effort.
@pasindur2, I would like to assign this task to you because you are interested in contributing. It would be helpful for you to become acquainted with our QA platform. Please do not hesitate to reach out if you have any questions. Let me know a time, let’s have an onboarding session.