Design & Develop
Articles
Bringing Continuous Testing to Your Organization Continuous testing means all your tests are executing all the time, providing continuous feedback into the quality and health of your applications. In order to achieve continuous testing, you must first adopt the right test automation strategy. Understanding how to bring in all different types of test automation practices as efficiently as possible enables you to get started down the path of continuous testing. |
||
A Simpler Way of Using Machine Learning to Shift Testing Left The advantages of shifting left and testing as early as possible are obvious. But as you automate more testing, the test suite grows larger and larger, and it takes longer and longer to run. Instead, just automate the process of finding the right set of tests to run. The key to that is machine learning. This isn't AI bots finding bugs autonomously without creating tests; this is a different way to use machine learning, and it’s far simpler. |
||
Inverting the Test Automation Pyramid A growing company was tasked to develop a test automation program from scratch, change its coding practices, and build a continuous testing toolchain. Martin Ivison details how they did it, including realizing that implementing the traditional test pyramid wasn't going to work—it would have to be turned upside down. They found out that small is beautiful, cheap is good, and cultural change matters. |
||
Test Everywhere: A Journey into DevOps and Continuous Testing A move to DevOps creates an opportunity to shift the testing process to the left. But what if you went further? DevOps supports continuous testing, so you can advocate for a constant focus on quality, with testing permeating the entire software development process. Here's how you can actually have a faster testing process when the software is tested throughout the lifecycle, by developers, testers, and automation alike. |
||
6 Steps for Succeeding with Test Automation in Agile Lots of test automation efforts in agile software development fail, or at least do not maximize their potential. This article looks at two main reasons test automation may not live up to the expectations that testers and other stakeholders in the agile development process have, then outlines six steps to avoid falling into these traps. Here's how to succeed with test automation in an agile environment. |
||
From Performance Tester to Performance Engineer Many performance testers think that after a few years of experience, they automatically become performance engineers. However, it isn't that straightforward; the route to becoming performance engineer is a long and continuous journey. This article details the many things performance engineers need to do beyond performance testing, and it gives an outline for steps to take to advance your career. |
||
Who Should Set Up Continuous Integration for Automated Tests? If you want to trigger long-running, end-to-end automated tests, you must integrate the test execution system with the continuous integration system. But this job falls in a fuzzy area that meets at the nexus of feature development, test automation development, quality assurance, and build and release engineering. Here's how to decide who should be responsible for the setup. |
||
Shifting Right Offers New Possibilities for Agile and DevOps Teams The shift-right concept originates from testing. But agile and DevOps teams also can use it to improve their systems and service to the client. However, there is a complicating factor: Different people have different explanations for what shifting right is. Let’s look at the different forms of shifting right, what the potential benefits are, and who should ideally be involved in your shift-right process. |
||
Simplify Continuous Operation Tests with a Periodic Reboot 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. |
||
Shifting Your Testing: When to Switch Gears Shifting your testing either left or right can meet different needs and improve different aspects. How do you know whether to make a change? Let your test cycles be your guide. Just like when driving a car with a manual transmission, if the engine starts to whine or you’re afraid you’re about to stall out, switching gears may be just what you need. |