Which browsers should we test on while doing Cross-browser testing (manual/automation)?

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 at these figures (https://designadvisor.net/blog/shopping-cart-abandonment-stats), 75.6% of checkouts are abandoned, and 17% of those are attributed to the website had errors or crashed (https://kinsta.com/blog/shopping-cart-abandonment).

Comments

How to Unzip files in Selenium (Java)?

1) Using Java (Lengthy way) : Create a utility and use it:>> import java.io.BufferedOutputStream; import org.openqa.selenium.io.Zip; import java.io.File; import java.io.FileInputStream; import java.io.FileOutputStream; import java.io.IOException; import java.util.zip.ZipEntry; import java.util.zip.ZipInputStream; public class UnzipUtil { private static final int BUFFER_SIZE = 4096; public void unzip (String zipFilePath, String destDirectory) throws IOException { File destDir = new File(destDirectory); if (!destDir.exists()) { destDir.mkdir(); } ZipInputStream zipIn = new ZipInputStream(new FileInputStream(zipFilePath)); ZipEntry entry = zipIn.getNextEntry(); // to iterates over entries in the zip folder while (en...

The use of Verbose attribute in testNG or POM.xml (maven-surefire-plugin)

At times, we see some weird behavior in your testNG execution and feel that the information displayed is insufficient and would like to see more details. At other times, the output on the console is too verbose and we may want to only see the errors. This is where a verbose attribute can help you- it is used to define the amount of logging to be performed on the console. The verbosity level is 0 to 10, where 10 is most detailed. Once you set it to 10, you'll see that console output will contain information regarding the tests, methods, and listeners, etc. <suite name="Suite" thread-count="5" verbose="10"> Note* You can specify -1 and this will put TestNG in debug mode. The default level is 0. Alternatively, you can set the verbose level through attribute in "maven-surefire-plugin" in pom.xml, as shown in the image. #testNG #automationTesting #verbose # #testAutomation

ChainTest Reporting Framework (ExtentReports is being sunset)

ExtentReports is being sunset and will be replaced by ChainTest Reporting Framework. 1. What is ChainTest? ChainTest is an open-source test reporting and analytics framework designed to enhance the way QA teams manage and analyze their test results. Think of it as a central hub for all your test data, offering: Real-time analytics : Stay updated with the latest test outcomes. Historical reports : Compare results over time to identify trends and improve processes. Static reports : Easily share detailed HTML reports with stakeholders. Multi-project dashboards : Consolidate data from different projects into a single view. This tool is designed to integrate seamlessly into your existing testing workflows, providing both flexibility and scalability. 2. Why Use ChainTest? Let’s talk about why ChainTest stands out: Enhanced Visibility : Gain clear insights into your test execution metrics, helping your tea...

My Testing Thoughts

Search This Blog