"BDD In Action" is a book that aims to cover the full spectrum of BDD practices from requirements through to the development of production code backed by executable specifications and automated tests.
This article explains why Paddy Power adopted continuous delivery (CD), describes the resulting CD capability, and reports the huge benefits and challenges involved. This information can help practitioners plan their adoption of CD and help researchers form their research agendas.
Priyanka presents some of the advantages and challenges that agile adoption brings for testers and testing and presents some ideas on how to overcome the obstacles and leverage the advantages. She discusses the agile tester mindset and how the role of someone doing testing in an agile environment changes.
The second edition of Stephen Nelson-Smith's book "Test-Driven Infrastructure with Chef" describes a testing workflow and tools for writing fully tested infrastructure code
The process of developing an automated functional test solution is not much different from the process of creating the same program but Preparation and definition of the best practices are critical. 3
“ATDD By Example” value proposition was to be an introductory hands-on guide to implementing and successfully applying Acceptance Test Driven Development (ATDD) from zero.
Mustafa Saeed Haji Ali demonstrates how to automate black-box acceptance and functional tests using SpecFlow. 4
“Experiences of Test Automation” is a compilation of experiences in the field from a multitude of organizations and technologies, including both obstacles and achievements, successes and failures.
Rajneesh Namta shares his thoughts, experiences, and some of the critical lessons learned while implementing software test automation on a recent Agile project. 7
InfoQ have talked to Dan North, Gojko Adzic, Elizabeth Keogh and Matt Wynne about Specification by Example, Executable Specifications and Feature Injection and how they relate to BDD. 1
TekPub is an interesting case about company who started on ASP.NET MVC and quickly moved to Ruby on Rails. We had the opportunity to talk with them about their technology turnaround. 21