Testing Initiatives for APM

This is an issue for the discussion on how to improve collaboration with SET counterpart and increase testing efforts for APM. In order for the team to move faster while ensuring quality, I would like to leave a few suggestions to kickstart the discussion:

• 🏁 Verificathon where the SET dedicates half or full-day bi-monthly to do extra verification on top of the effort done by the engineer. Issues are batched and tested, ideally those that have workflowverification or closed within the milestone.
• ✅ Test scenarios checklist on the MR done manually by the engineer. This is to ensure certain scenarios were covered and thought through before opening the MR. In many places, it is the job of the test engineer to do so, but it would become very soon a bottleneck. Nevertheless, there is a lot of value in the awareness that comes from writing down a quick list of scenarios.
• 📆 @ClemMakesApps, @mnohr and I had a test sync meeting where we discussed some of these suggestions ☝ Should we have it as a team, bi-monthly to sync on testing, ~bug issues, and regressions? Would it be better to have it only on an issue?
• 🐛 regression retrospectives in issues where we do an RCA (Root Cause Analysis)

@ClemMakesApps suggested identifying past regressions/bugs that weren’t caught in tests to better understand what the gaps are and to determine solutions and I think it also could be a great place to start.

Any suggestions, ideas, concerns?