continuous integration
 |
What We Talk about When We Talk about Test Automation Testers talking about test automation often mean browser automation. Developers are probably talking about unit testing or something at the service layer. And operations people are most likely thinking of monitoring and the guts that control continuous integration. But the practices are more important than terminology. |
|
 |
3 Major Continuous Delivery Hurdles Teams Need to Overcome Teams that leverage continuous delivery and continuous integration are playing an entirely different game than software teams of the past—instead of mapping out this major, ridged timeline, data is being both gathered and used more frequently (and effectively) than before. |
|
 |
Becoming a Modern Software Tester Testers today need to look more like developers than users. Automation is becoming essential, so understanding at least basic programming is a must. As companies adopt agile and deliver more frequently, modern testers should learn to code, understand continuous integration, and use tools to eliminate constraints. |
|
 |
Continuous Integration Makes Testers Look Like Developers There have always been distinct lines that separate developers and testers—and they didn’t often work all that close together. However, shifting everything to the left and being more concerned with testing at every single stage of development has blurred the line between their responsibilities. |
|
 |
Data-Driven Testing Skills in an Agile and DevOps World For agile and DevOps, an understanding of the role of data analysis in the test strategy is helping teams accelerate development, testing, and deployments. As we continue to enhance our testing effectiveness, data analytics skills are an important dimension in managing risks in a “continuous everything” world. |
|
 |
The Key Areas Where Testers Need to Grow With new methodologies, technologies, and innovations constantly being introduced, testers need to continue to push forward with an open mind and an understanding of different disciplines to make sure they have a rock-solid standing in the process. |
|
 |
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. |
