Report Portal has proven itself very useful for pinpointing and troubleshooting what commit(s) potentially introduce regressions, but we aren't proactive in monitoring the test results. The pain this causes is when we try to do release readiness activities, it's more difficult and time consuming to determine if a failure is a flaky test or an actual regression.

The purpose of this card is to investigate options for how we could start getting more proactive visibility into post-stage test failures and come up with some ideas on how we bake evaluation of failures into our day-to-day (or week to week even?) process. Some ideas for some options would be email notifications, slack messages, etc. Currently report portal already has the capability in its settings to send email notifications to certain recipients about run completions and possible failures.

This supports our eventual goal of being able to release every sprint.

Timeboxed: Up to 3 days.