The goal of this task is to identify which parts of our codebase and features of the site are covered by browser tests. We'll use the information to make a decision on whether to create more tests or remove obsolete ones.
- Create a user facing feature matrix of MF or update the one we already have: [insert link here, I cannot find it]
- Create an efficient method of mapping browser tests to features. This will be useful to identify coverage this time and in the future if we decide to do such periodic tests.
- Match features with browser tests. The outcome is some kind of a table where on the X axis we have features, and on the Y axis we have browser tests.