In our modern digital society, data is abundant, and storage is affordable. Businesses, governments and even individuals can (and do) collect every transaction, click, swipe, location, message and attribute in their datasets. With just a few clicks on my smart device, I can review data on every place I’ve been, how much I spent, every step I took, what the weather was like and who I was with. Businesses collect the same abundance of data.
A good browser, good apps, a good camera, and fast networking in your smartphone are just expected today. – Thorsten Heins This quote shows the dependency we have on browsers, the web, and mobile phones today. But how did we come so far? Technological development and robust testing have helped us reach where we are. When it is about multiple devices and browsers – the role of cross-browser testing can not be under-estimated.
Cross-browser testing is performed to be sure that your product is working as expected on the various device, platform, and browser (and their versions) combinations that your customers might be using. With a plethora of devices and their versions in the market, it is integral to perform stringent cross-browser testing to attain a good market capture. Is it easy? No! Is it necessary? Absolutely yes! However, the pain and efforts associated can be reduced, if the cross-browser testing is cloud-based.
The whole point of cross-browser testing is to deliver consistent user experiences across various browsers. When we build websites or web apps, some of their features aren’t compatible with some browsers; with cross-browser testing, we can ensure uniform experiences. While performing cross-browser testing, we generally check for the following: When we perform cross-browser compatibility testing, it’s easy to discover such bugs and fix them before our product goes into production.
Let’s face it: In today’s modern world of cloud and containers, there are still thousands of legacy applications that were not written with an API-first approach. Some legacy systems can still provide tremendous value today, but the means for accessing them are completely out of date, thus rendering them almost useless.
There are two types of Ruby Begin and End blocks. A simple Google search of “Ruby begin end blocks” will lead you to either of these two kinds of articles – the ones in all caps (BEGIN and END) and the ones usually separated by a slash (begin/end). Both of these are different things but confused with the same name. In this post, we will dive into both. Here’s an outline of what we’ll be covering so you can easily navigate or skip ahead in the guide –
The RESTful web API has long been the industry standard, but in recent years, APIs based on the GraphQL Schema Definition Language has grown in popularity. This post will go over the advantages and disadvantages of each, as well as when GraphQL makes sense for your application.
Sometimes I walk through the grocery store and marvel at the way customers float through the aisles, blissfully unaware of the logistical nightmare it probably took to stock the shelves. They have no idea how many people, systems, and modes of transportation it takes to make everything magically appear on their grocery shelves. But I do. As the Senior Director of Software Engineering at KlearNow, I spend my days preserving the bliss of those grocery shoppers.
Welcome fellow developer, I can see you’ve traveled a long road, why don’t you stay a while and listen? I’ve got some fantastic stories to share; Lessons to imbue your debugging skills with power and wisdom, adding at least 1000 XP to take you to the next level and make your future travels much safer. Hmm, now, where should we start? Have you already faced the terrifying Heisenbugs? They are truly fantastic.
