DevOps does speed up your processes and make them more efficient, but companies must focus on quality as well as speed. QA should not live outside the DevOps environment; it should be a fundamental part. If your DevOps ambitions have started with only the development and operations teams, it’s not too late to loop in testing. You must integrate QA into the lifecycle in order to truly achieve DevOps benefits.
Continuous operation tests find important bugs, partly as a result of their long operation and partly by increasing the probability of finding statistical bugs. However, CO tests have their own downsides. Mandating a periodic reset or reboot can work around these issues, as well as save time and cost for testing, reproduction, debugging, and fix verification.
The earlier you find out about problems in your code, the less impact they have and the less it costs to remediate them. Therefore, it's helpful to move testing activities earlier in the software development lifecycle—shifting it left in the process timeline. This article explores the shift-left methodology and how you can approach shifting left in your organization.
“Shift left” is one of the latest buzz terms in software testing. Movements like agile and DevOps recommend that testers shift left, but what does that mean, exactly? Here's how one tester became a believer in the shift-left movement; how he got his team's developers, analysts, designers, and managers on board; and how his entire organization has benefited from the shift.
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, Michael Nauman, a testing lead for AutoCAD Web, explains how we can go beyond basic agile principles. He digs into the current state of shift-left testing, the importance of aligning your DevOps with your automation, and using agile as a starting point on your quality journey.
In this interview, Melissa Benua, a senior technical lead at mParticle and senior backend software engineer at PlayFab, explains how the speed of development and testing has changed, as well as how to adapt to the new era of software.
In this interview, Adam Auerbach, vice president of quality and DevOps engineering at Lincoln Financial Group, explains how the role of testing has changed thanks to DevOps. He also talks about how testers can lead the DevOps movement through the power of automation.
In this interview, Andreas Grabner of Dynatrace explains why you need to pay attention to your users' needs when you're doing your performance testing. He shares his performance testing approaches and explores the top problem patterns that you can learn to spot in your apps.
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...