The web browsers we should be supporting should be the ones that our client and customers are using. We can easily get that information: To start with, get the analytics for the most used browser on your application and use that browser as the first candidate for your manual as well as automation efforts. If there are no analytics available for the current application, look for the analytics of similar application and if you are still clueless, use the worldwide statistics*: https://en.wikipedia.org/wiki/Usage_share_of_web_browsers Chrome: 48.7% Safari: 22.0% Firefox: 4.9% Samsung Internet: 2.7% UC: 0.3% Opera: 1.1% Edge: 1.9% IE: 3.9% *As of November 2019. We should select a subset of our tests that perform the functions that may break on different browsers and only run those many tests on all suggested browsers. It saves the total execution time of tests so that we can get your results faster and act quickly. For eCommerce sites, we need to be extra cautious. Look a...
A blog about my testing stories where I pen down my thoughts about test automation covering primarily Selenium, Java, Rest Assured, Karate, Maven, TestNG, Postman, newman, Jenkins, Git, Azure DevOps, etc.