Problem

Occasionally there are regressions that occur that we simply do not detect. This can happen because we don't test all the behaviour with every release, or it can happen because we don't test on every browser.

Solution

We could create a suite of basic integration tests that cover the core functionality of AdminCentral. 

The goal of the tests is

• detect any regressions that occur
• test on main supported platforms
• cover as much functionality as possible
• to not be too difficult or time-consuming to perform the tests
• to not be too difficult to time-consuming maintain the tests

Implementation

The tests could be automated with Selenium.

The tests could be performed manually. Manual is time-consuming - but has the advantage that it can be done immediately and is very flexible.
I think it makes sense to start manually, as a way to craft what should be included in the test. Once the test-script is refined (mature), then it can be  implemented in Selenium.
I would think we dont need a big process around the testing, simply a page with each script as a list of steps and expected results. The tester would simply create Jira tickets when steps did not have the expected results. It would then be a step in the sprint - to perform the integration tests. Any developer should also use the integration tests to verify that their changes did not break the associated area.

Proposal for test scripts

ShellApps and App navigation

Pages App

Assets App