Related Content
 |
Keeping Your Software Testing Abilities Relevant Today, Tomorrow, and Beyond Development and product teams have embraced agile and DevOps. What can testers do to keep up with their development peers? Here are some ideas about what testers can learn, what skills we can add, and what processes we can start doing in order to continue delivering quality today, tomorrow, and further into the future. |
|
 |
Choose Continuous Integration over Branching for Faster Feedback Continuous integration is the best way to get feedback often on the state of your project. Running automated builds and tests after each integration improves reliability and predictability. Consequently, using task and feature branches, while useful in some cases, can be a distraction and delay getting information. |
|
 |
Engineering Architecture Systems for a Faster Build In the era of continuous integration and continuous deployment, big applications are creating bloated build pipelines. The problem is when code becomes so entangled that every change impacts large portions of the system, meaning there’s a lot to rebuild. If you reshape the code architecture, you can reduce build times. |
|
 |
Make Your Security Testing More Agile Security practices traditionally have followed a waterfall model, adding security testing on at the end. Organizations need to coach their security programs and testers to prioritize analysis and risk, much like we do with agile stories, to better incorporate security defects with other feature work along the way. |
|
 |
Breaking Down Your Development and Testing Walls Testing earlier assures better quality. But maybe most important, things like agile and DevOps—which encourage that you shift your testing left and allow for more collaboration between different parts of your team—have broken down the walls that previously separated testers for the rest of the organization. |
|
 |
Finding the Bottlenecks in the Agile and DevOps Delivery Cycle To achieve incremental software development and continuous feedback, you need to eliminate the tasks that create bottlenecks, which hinder the flow of development. A chain is no stronger than its weakest link, and identifying these “weak links” is a critical step toward achieving agility and increasing efficiency. |
|
 |
Continuous Testing: New Improvements on an Old Idea The concept behind continuous testing is far from new, but what’s different now is that software development practices have evolved to a point where developers are embracing testing as part of their responsibilities. Testing is slowly moving from being an “event” to an activity throughout the development lifecycle. |
|
 |
Before You Can Eliminate Agile and DevOps Bottlenecks, You Need to Identify Them Agile and DevOps, which now dominate software development, lean on continuous integration, continuous testing, and continuous deployment. Because of that, anything that might break this iterative and continuous cycle could throw everything out of whack and stunt your team’s growth. |
