I think we really need someone to do QA for this. Could we collab with @jmatazzoni for some QA time on beta during our deployments?

Hi guys. This sounds valuable but I'm not sure I understand the project or the request fully. Can you say a little more, please, about what you have in mind to do and what kind of help you need?

Essentially, it's possible that changes to ORES can affect RC Filters. We'd like Collab's help reviewing the filters functionality when we make deployments (our usual cadence is once every 3 weeks or so). This would involve checking on the functionality in Beta and reporting back if anything was broken.

This seems like it would be at last partially testable with selenium running against beta cluster.

• We could do browser testing on a schedule or on a commit (in ORES service or Ext.)
• We could have a QA specialist look at stuff in a browser for deployments
• We could add a simple check of RC/WL/etc. for ORES Service Deployments and ORES Ext deployments.

We talked to @jmatazzoni and @Catrope. They agreed that Collaboration should look into implementing these types of browser tests. So we (Machine-Learning-Team) will keep monitoring. Note that manual checks are currently part of our deploy pattern.