Testing in Continuous Delivery: Shift Left
Testing in Continuous Delivery: Shift Left
To shift left is to shift tools and knowledge to earlier phases in the engineering process. But what does this mean for each stage of continuous delivery?
Join the DZone community and get the full member experience.Join For Free
Learn more about how CareerBuilder was able to resolve customer issues 5x faster by using Scalyr, the fastest log management tool on the market.
In today’s constantly changing market, continuous delivery is one of the most popular engineering approaches: most companies claim they work according to CD rules, or at least don’t say out loud they don’t. The popularization of this methodology comes from its main idea: an engineering process based on short, repetitive iterations, where every iteration ends with delivering user value and getting feedback from it.
Knowing the main rules of the continuous delivery approach, how do we deal with testing and quality assurance in such a fast and repetitive process?
Get Rid of the Walls
Let’s consider a simplified engineering process based on the following consecutive phases: specification, development, testing, and operations. From a quality assurance perspective, the problem is that testing is the last phase before shipping features to the users, which is often too late, especially if we’re dealing with the iterative nature of a continuous delivery approach. Throwing changes over proverbial wall to another team is no longer effective, and causes bottlenecks in the whole process due to handover times. We don’t want to separate analytics from the development team during the specification phase. Furthermore, we’d want to find bugs already in the development phase, not when the implementation is already done. Keep in mind also that the aim of our quality efforts is the production environment, so we want testers to be able to get end users’ feedback and deal with production configurations.
The concept that follows those approaches is often called shift left, which means shifting tools and knowledge to the left, to earlier phases in the engineering process.
How does a shift left approach fit for testers in agile teams? Let's consider every phase of our simplified development process from a tester’s perspective.
As we’ve already said, the whole development team (which testers are part of) should participate in creating story specifications. But how can we assure quality and prevent defects in such an early phase, before implementation? A crucial difference between the traditional approach and testing in continuous delivery is that testers are creating a strategy for the whole process, not only executing given scenarios. Part of this is to outline a testing approach already in the specification phase, in form of simple testing notes. These don’t have to be full blown testing scenarios, rather notes about critical quality aspects and things to keep an eye on.
This exercise certainly lets us share testing knowledge through the team, but what’s even more important is having the whole team focusing on quality, which helps to prevent a lot of defects before we even start development.
Following shift left practice, we don’t want to wait with testing for development to be done. Finding bugs in your code should be done in parallel with writing it.
One way to achieve this is to test small pieces of implementation. We can divide it into testing the back end and front end separately (and the whole piece together), but we can go even deeper here, and test isolated parts of back end code with other modules being mocked based on contract. This idea of testing smaller chunks of code requires close work with the developers and a good understanding of your system back end architecture.
Another idea is to pair testers and developers. Testers often come to pair programming unwillingly - just like testers are more experienced in testing, developers are usually more experienced in writing code. But testers bring to the table a unique way of looking at implementation, which is quality and end-user perspective. This special combination of technical and domain knowledge makes development more defect-proof and user-oriented.
Let’s remind some fundamentals of continuous delivery, which is development process based on short and iterative cycles. There’s no way to achieve this while having testing phase as a manual process. One of the keys to continuous delivery is automation and testing is no exception - you should have most of your checks automated. Of course, it doesn’t mean that you must cover every edge case of your application with expensive end-to-end tests. Test engineers should have the best knowledge of which parts of the application should be covered with, for example, functional Selenium tests, when to use back end integration tests and when unit tests are just fine. Sounds familiar? Yes - it’s a test pyramid. Our goal is not to maintain the largest number of tests, but rather to get quick and stable quality feedback.
Does it mean that there’s no room for manual tests in continuous delivery? Remember that there’s always going to be some number of tests that are very expensive to automate, and at the same time, very important from a business perspective. Having most of our tests automated gives us time to fully concentrate our manual efforts on the most crucial domain and exploratory validation.
Operations phase usually means going to production. If our features are in production environments, does it mean it’s the end of the quality cycle? Remember that big part of the continuous delivery methodology is getting end users’ feedback.
A straightforward way of collecting this kind of feedback is application logs. We should always make sure that we have proper business-level logs - they’re our way to reproduce and trace how users interact with our product. Application logs usually come in a pair with metrics: CPU, disk, latency, etc. Those are another important gauges that give an instant feedback on our application health.
An approach that is getting more and more attention lately is testing in production. One would ask: isn’t it the single worst practice? But we’re not talking here about throwing untested changes to production environments and waiting until something goes wrong. There are various techniques of production testing, such as canary releases, where we introduce new features only to a limited range of production users, who give us feedback with minimized risk. Remember that this limited range of production users can also mean your single test user - this way you’re gaining the ability to test your features in full isolation on production configuration.
Dev, Test, Ops
Arguably one of the most hyped terms in the development world right now is DevOps. The origin of this term comes directly from the shift left concept, and it means giving tools and operations responsibilities to developers in order to reduce bottlenecks and handover time.
There are also other very similar terms - TestOps and DevTestOps. With this approach, you start quality efforts with early stages of development and extend them also to production environments. When we’re considering this kind of approach, the term that describes such practices even better is continuous testing. It’s a group of techniques where testing means building and implementing quality assurance strategy throughout the whole development cycle, not only in single testing phases.
The continuous delivery methodology provides many new challenges for test engineers. With the iterative development approach, it’s important to maintain the quality of the product in every phase of the cycle. This approach is often called continuous testing - this means testing from the very first phase, reducing bottlenecks and handover times by combining various tools and practices. It is also ones associated so far with different roles in the engineering process. Testing in continuous delivery means building and maintaining a quality assurance strategy in the whole development cycle, and in every phase.
Published at DZone with permission of Łukasz Rosłonek . See the original article here.
Opinions expressed by DZone contributors are their own.