Blog

Quality control is obsolete. The spread of Agile, DevOps, and shift-left approach has pushed traditional QC out of businesses’ practices. We now have continuous improvement, user acceptance testing, and total quality management. Each of them strives to eliminate post-factum checks. And the ultimate goal for organizations today is to be as proactive as possible. Yet, quality control testing isn’t lying curled up in the corner and barely breathing. It’s the most alive it’s ever been. You just may not have noticed how it has changed. So, let’s find out how to use it now.

What Is Quality Control Testing?

Originally, QC was a dedicated, post-release phase where a team checked a product’s quality. The purpose of this retroactive inspection was to see how well the preceding activities were carried out. For example, you could pinpoint how effective your testing was by looking at how many defects were present after completion. Quality control in software testing acted as ...

Be honest, if your phone disappeared right now, your world would be in shambles. Data access, payments, GPS, calls, apps… We rely on our devices for nearly everything. And for many, that small metal gadget is the difference between feeling secure and comfortable and wanting to cry in the corner. And the number one threat to your customers’ happiness and your business’ prosperity is poor mobile app security testing. For over five years, cyber security issues have been the number one risk for companies. And as more people become increasingly aware of the cruciality of digital protection, their demands for online safety grow sharper. So, today we discuss the big and tiny things that make your mobile security testing meaningful and practical.

What Is Mobile Application Security Testing?

On the technical side, mobi...

Teams have a love-hate relationship with Android. It’s highly customizable and has an incredibly vast community and toolkits. It’s indeed a very flexible OS. And that’s where the hate part comes in – working with devices that could rival human cells in their quantity. For that reason, automated Android testing has become a staple in QA resources. But there’s something else that should take its place: high-quality, expertise-driven automation. Yes, automated software testing services are, without exaggeration, a miracle for many companies. Yet, it wouldn’t lead anywhere without skill and domain mastery. Today, we discuss the little things that make your Android automation testing go big.

The Nuances of Android App Automated Testing

First and foremost, your team needs to know Android quirks by heart. And they need to understand them like basic math (one plus one isn’t two and a half). In the worl...

Apple applications are easy to test. Compared to Android, that is. But when it comes to automated testing for iOS, that’s an entirely different kind of battle. This fruity operating system is cluttered with peculiarities no other OS has. And working with it calls for precise expertise and practices. Today, we discuss the special approaches to iOS automation testing that turn it from a brave fight into QA delight.

Key Challenges in iOS Automated Testing

First, we need to get to know the source of pain for QA engineers automation testing iOS apps. We’ll focus on the OS’s peculiarities. But you also need to keep in mind the universal challenges of working with automated testing (AT).

Device Fragmentation

Apple has well over a hundred mobile devices for...

Result-driven QA isn’t always about planning and strategizing. Sometimes, the best thing for your product is getting a cup of coffee and playing around with it. This relaxed approach to testing, though well known, is still not as widely used as it should be. So, today, we discuss the miracles of exploratory software testing and how and when to apply it.

What Is Exploratory Testing?

Exploratory testing is an improvisational investigation of your app. QA engineers rely on their skills and knowledge to look around it without following defined test cases or scripts. Typical QA procedures are highly structured. And you can only systematically look for issues you can predict. Exploratory testing, by definition, strives to cover the unknown, obscure processes or user paths. Such a Voyager-esque method lets you better secure critical areas and add an extra layer of quality to your product. Yet, exploratory testing isn’t necessarily a supplementary addition to a regular QA proces...

A flimsy UI doesn’t lead to customer frustration, negative reviews, and high churn. When people encounter a sub-par interface, they just move on. They won’t waste time and energy on interacting with a project in any way. So, while in life we try to control our first impressions, in software, they’re everything. In fact, UI/UX issues are top-of-the-list reasons for deleting an application. That’s why every company making an Android app deserves utmost respect (and gentle condolences). They have to meet strict user expectations. And they must navigate the insanely diverse technical landscape of the little green man’s OS. Today, we talk about doing all this with grace and in a way that makes users go heart-eyed.

Android...

Good communicators tend to do much better in life. And this applies to software as well. So, for your product to perform at its finest and conquer the market and the users’ hearts, API load testing is a must.

What Load Testing APIs Means for Your Business

To better understand the significance of today’s subject, let’s take a step back. As you know, APIs act as small communication centers for your software. They allow it to exchange data with other apps, services, and systems. And to briefly answer the question “What is API load testing?” – it’s the practice of evaluating how well an API handles its job. For example, it can investigate how many users your API can process, how it works with data it transfers in terms of speed and accuracy, etc. Basically, APIs are your communicators. And API load testing teaches them to be good ones. Now, instead of rambling about how important performance testin...

You can’t know if anything is wrong until a problem pops up. That’s what someone who is fine with an alright product might say. This article, however, is all about proactivity that guarantees a gem of a project. Today, we talk about software quality assurance audit.

Quality Assurance Audit Process

Most likely, you already know what is a quality assurance audit. But if you need a refresher, let’s briefly review the QA audit’s meaning. Software quality assurance audit is the assessment of QA activities and processes within a software development environment. It’s carried out to check their efficiency, productivity, compliance, etc. To answer the question “What is a QA audit?” very concisely – it’s evaluating how good your quality-related activities are. If you feel like you need more info on this subject, feel free to check our page on software QA consulting and audit. But for now, we move ...

What is the root of quality in software? A good budget, a smart strategy, customer centricity… All are valid answers. But they would be useless without skilled execution. From a QA perspective, quality is how well you examine your app. If you check every corner of your product and make sure it all works as needed, then you’ll achieve the results you envisioned. That’s why the value of your project is directly linked to your test coverage.

What Is Test Coverage?

Technically speaking, test coverage is a collection of metrics that determine how much of your app was investigated by your test cases. Let’s take a look at a brief example. Imagine you’re testing a calculator app with four functions:

• Add.
• Subtract.
• Multiply.
• Divide.

You run a few tests to check if the addition and multiplication features work properly. But you haven’t tested subtraction or division yet. This means you have low test cove...