Browser update regression testing
The test case suite should be made up of those test cases which have the highest priority. These are any scenarios which, if failed, would eliminate all or a major part of functionality, as well as those tests directly related to the browser updates in question. These latter tests tend to be developed shortly before the test cycle begins.
Testing against update is a form of compatibility testing, its purpose is to ensure that the webpage or browser dependent application has not been driven out of compatibility by changes to the browser. In this respect, it is no different than any other form of compatibility testing. It should be remembered that development doesn't end with a shipped product or when a website goes live, as changes in the digital environment require ongoing adaptation.
The increasing number of browsers has raised the importance of cross browser testing and regression testing of applications and sites against browser updates. Fortunately, only about five browsers account for the majority of traffic. While this cuts things down a bit, there are still numerous variations of each browser, with more being issued as updates of current versions are ongoing.
Testing against update is more than just a test for compatibility. It is a form of functional testing as well. One of its major purposes is to establish that updates do not “break” the site or the program and that at least an acceptable level of function is maintained after the transition.
Modern business requires a website and an increasing number of businesses are using apps as part of their business model. Testing against update enables businesses to be certain that their digital presence is not erased or damaged by the normal improvements common to the digital ecosystem. It's a kind of directed evolution where the digital environment changes and websites and applications change in response. Which makes testing against browser updates an important part of that evolution.