Create Testing checklist before merging a PR #2171
Replies: 4 comments
-
Test scenarios are available. However, there are three challenges. 1, No one checks whether these test scenarios are not sufficient or validated. There are several possible ways to automate testing, but do we need to prepare for it with both old and new GUIs? |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
I agree. Once the checklist is stable, we can use an E2E testing framework (Cypress?) to automate each case in the checklist. |
Beta Was this translation helpful? Give feedback.
-
The interface, new UI. Is useless loose time with older one. |
Beta Was this translation helpful? Give feedback.
-
At present, we don't do a thorough check on the impact of a new feature/change/fix on all the existing features that are working. This is breaking things intermittently and demands additional effort in fixing it (E.g. Moderation feature not working for comp & releases now). This cannot happen this way and we need to find a quick solution here. I propose that we prioritize this tasks asap.
discuss in today's (Nov 8th) meeting
Beta Was this translation helpful? Give feedback.
All reactions