Background

In order to better understand the value of the browser tests we've written thus far – and to understand, say, the benefit of investing heavily in T224947: Daily Minerva Selenium test job failing – it'd be good to understand which features we have covered and by how much.

@Edtadros correctly referred to this as an inventory, which should include:

• The features under test
• Per feature:
  • What functionality is covered
  • What functionality isn't covered
    • e.g. We don't have a test that covers that clicking the watch star adds a page to your watchlist
  • Whether the feature has associated tags

AC

• An inventory (as described above) is created for the MobileFrontend extension and committed to the repository
• An inventory (as described above) is created for the MinervaNeue skin and committed to the repository