George Ukkuru is a seasoned technocrat and AVP of quality engineering, DevOps, and SRE @Marlabs Inc. Over the course of two decades, he has helped Fortune 500 companies implement Agile testing practices. He has also authored a number of books on quality engineering and test automation. In this QnA, Ukkuru lays out the scope and depth of his experience without even trying.
As a small business or a startup, we often make decisions that can change the whole structure of our working processes. Honestly, this is not a bane that can bring the businesses down. Such businesses thrive on these decisions as they let them clearly decide what suits them best and why. What’s better than finding it on their own by trying a mix of things? As for this post, it is a bit different from startups and small businesses.
Rahul Parwal is a software engineer, speaker, mentor, and writer out of Jaipur, Rajasthan. He has dabbled in software development, testing, and automation, and often shares his learnings in his blog. In this QnA, Rahul makes the point that a randomly failing test is always worth investigating and that assumptions are dangerous in testing.
In this series, real (and really good) QA practitioners use their experience to support—or debunk what you might know about software quality. James Espie is a test specialist, a quality engineering proponent, and a continuous learner from Auckland, New Zealand. He shares his insights and sporadic bursts of inspiration in a hilarious newsletter called Pie-mail. If you haven’t seen it, you should check it out.
Did you know that an average user takes only 0.05 seconds to form an opinion on a website? Yes, Sweor’s study on website statistics shows that users decide whether they want to use a website or not in a fraction of a second. We can also note that about 57% of the global population doesn’t recommend non-responsive websites in the same study. In general, most websites or web apps run into errors because of a solitary reason: solid cross-browser testing isn’t performed.
Today, there are 1.88 billion websites on the internet and the number is rapidly increasing. There are 3.8 billion people in the world that own smartphones today – which amounts to 48.16% of the world population. The internet traffic from mobile (as compared to that from desktops) has also been increasing, and now stands at 56%. The point I am trying to make is that if you have a website – it can be accessed from a web browser or a mobile browser.
Today, according to w3c, the most frequently used browsers are Chrome, Edge, Firefox, Safari & Opera. It is always advisable to run cross-browser test cases at least on these. However, the process of analyzing and selecting the thousands of device, OS, and browser combinations requires time, expertise, and effort too. Additionally, deciding which cross-browser test cases are ideal for automation requires proper analysis and expertise. Let us explore a few of such cases in this article.
Let’s start this post with a situation. An organization working in the logistic business has started to gather positive reviews and millions of users are now opting for their services through their mobile app. In other words, the organization is scaling very fast. Even though they were managing quite well with manual testers and in-house test automation setup, they know this arrangement cannot work for long. They are smart people.
