Recent Posts

Consumer Electronics Are Now App Driven. So, Who’s Handling the QA?

Consumer electronics have become part and parcel of our lives. Projected to reach a market value of $415,897 million in 2021, consumer electronic businesses are constantly innovating by leveraging emerging technologies, like smartphones, to find a differentiator that gains them a competitive edge in a highly competitive market to create an increase in customer satisfaction and retention.

Continue reading

The Culture Shift to Developer Testing

Introduction

This is part 2 of a 2-part piece on the culture shift to Developer Testing. Part 1 covered the difference between “culture” and “practices” and their implications for your teams; it also examined the origins of “Developer Testing,” and discussed how much testing is a Developer’s responsibility. Part 2 will begin by exploring various cultural aspects of popular development methodologies with recommendations on how to successfully implement said cultural practices in your own teams; it will conclude by emphasizing the importance of getting culture right within your teams with 5 first-steps you can take. So, without further ado, let’s dive into part 2.

Continue reading

The Culture Shift to Developer Testing

Introduction

Developer Testing is a trend in software development that aims to improve delivery speed and reduce costs. It’s important to note that there isn’t an exact definition of what Developer Testing is; it is going to vary from organization to organization, with some having Developers take over more of the testing tasks and others have Developers take over all of the testing tasks. It could range from more unit testing by Developers to testing full end-to-end workflows. No matter the case for your organization, to have success in moving testing tasks to Developers is reliant on a culture that supports this—not just implementing a new tool or saying, “Okay, Developers, now you get to test!”

Continue reading

Self-Healing Automation: A Remedy for Failing Automated Tests

In CI/CD environments, automated tests are the linchpin of a successful build and deployment. When tests go bad, they cause failed builds, necessary research, and examination. And, of course, if there is a real error, the need to be fixed and rerun. However, what often happens is that a test changes slightly or the underlying environment changes in a way that may cause a test to fail at certain times but not others. These situations are frustrating and I often mutter to myself, “Can’t the test figure these things out on their own?” Today, the answer is “Yes, they can!” Or, at least they can to a point.

Continue reading