Automated acceptance testing reduces time wasted in manual testing and bug fixing, and when combined with Behaviour-Driven Development, can guide development effort. But it requires skill, practice and discipline. The Screenplay Pattern helps teams address these difficulties and is where you may end up by mercilessly refactoring Page Objects using SOLID design principles.
Moving your release cadence from months to weeks is not just about learning Agile practices and getting some automation tools. It involves people, tooling and a transition plan. Derek Weeks discusses some of the benefits and approaches to getting there.
Banks score high in some challenging areas for DevOps adoption: culture, architectural readiness, agile maturity and technical best practices. They score lower in technical and process based areas. 5
The Internet of Things is poised for huge growth and will be one of the key building blocks of digital technologies. Thread is a network protocol to connect various devices within your home. 2
InfoQ asked Matthias Marshall what's new in the 2nd edition of his book and his view on the evolution of the configuration management tool space.
In the book Leading the Transformation executives Gary Gruver and Tommy Mouser share their experiences with applying lean and agile development methodologies in enterprise development teams.
In the article Alexander responds to the questions about the difference between test frameworks and test scripts and discusses an approach for how test a automation solution could be implemented. 4
As infrastructure becomes code, reviewing (and testing) provides the confidence necessary for refactoring systems. Reviews also help spread consistent best practices throughout the organization.
This article discusses the key questions to be contemplated by your enterprise in determining whether Git is right for you and what you need to consider in moving to Git.
The book Fifty Quick Ideas to Improve Your Tests provides suggestions that cross functional teams that are doing iterative delivery can use to manage and improve their testing activities.
With desired agile team traits like self-organising, role blurring and skill diversification, do we still need Test Managers in agile? How are the activities which have long made up the role divested?