Teams everywhere are looking to speed up testing without sacrificing quality, so once again, some of the top articles last year were about continuous integration, machine learning, and—of course—how to best implement and use test automation. But readers were also interested in what they shouldn't be doing, with two high-ranking articles about test practices we should stop and a tool you may be misusing.
Many people misunderstand the purpose of Cucumber. Because it seems to yield clearer, plain-language test scripts, testers want to use Cucumber as a general-purpose testing tool, including for API tests. But its true purpose is as a BDD framework. You may be thinking, what’s the harm? Here’s why it makes a difference—and why you should choose another tool for API testing.
Many testers spend their time doing functional testing and don't come out of this cocoon. But software testing is all about discovering quality-related information to assist stakeholders in making informed decisions, and there are multiple ways to discover information in addition to functional testing. Here are six actions that will help you add more value to your projects.
There are many metrics to measure the effectiveness of a testing team. One is the rejected defect ratio, or the number of rejected bug reports divided by the total submitted bug reports. You may think you want zero rejected bugs, but there are several reasons that’s not the case. Let's look at types of rejected bugs, see how they contribute to the rejected defect ratio, and explore the right ratio for your team.
The internet of things (IoT) continues to proliferate as connected smart devices become critical for individuals and businesses. Even with test automation, performing comprehensive testing can be quite a challenge.
In this interview, Paul Grizzaffi, a principal automation architect at Magenic, details the parallels between software testing and heavy metal music, as well as the issues that arise when management places unrealistic expectations on automation engineers.
In this interview, Geoff Meyer, a test architect in the Dell EMC infrastructure solutions group, explains how test teams can succeed by emulating sports teams in how they collect and interpret data. Geoff explains how analytics can better prepare you for the changing nature of software.
In this interview, Gil Sever, the cofounder and CEO of Applitools, explains the importance of automation in modern testing, why you need to be customer-obsessed, and how your UI can determine the success of your applications.
In this interview, Dawn Haynes, CEO, testing coach, and consultant for PerfTestPlus, explains how the different yoga poses relate to testing, why you need to adapt to your testing situation, and how to succeed in the nonfunctional testing space.
Risk-based testing is essential to focus our testing, but it is not always easy to apply to our projects. Risk management tends to focus more on project and process risks (i.e., Will we make the deadline? Do we follow our processes?) and less on the product risks that can act as a foundation for a risk-based approach to test. Including this aspect of risk in your test coverage will give you a solid foundation for defining a test strategy that implements and executes the right tests with the right intensity to mitigate the most critical product risks. In this presentation, Gitte Ottosen walks you through approaches to lightweight product risk analysis that can be applied whether you are working in a traditional or agile context. The approaches focus on the conversation around identifying and classifying product risks as a team effort, as well as how to use product risk analysis to support test specification and execution.
Today’s IT systems communicate with customers through multiple points of engagement and various interfaces, ranging from web, mobile, and voice to BOTs and apps like Alexa and Siri. Sanil Pillai says these systems need to provide seamless handoffs between different points of interaction—while at the same time providing relevant and contextual information quickly. To accomplish this, a team must be able to successfully pair device hardware capabilities and intelligent software technologies such as location intelligence, biometric sensing, and Bluetooth. Testing these systems and interfaces is becoming an increasingly more complex task, and traditional testing and automation processes simply don’t apply to new-generation digital interaction services. Join Sanil as he discusses the testing and automation challenges in new-generation digital interactions using hyperconnected BOTs.
As more applications are hosted on servers, they produce immense quantities of logging data. Quality engineers should verify that apps are producing log data that is existent, correct, consumable, and complete. Otherwise, apps in production are not easily monitored, have issues that are...