InfoQ Homepage Behavior Driven Development Content on InfoQ
-
Who is in Charge of Quality in Software Development
As silos break down, the whole team is responsible for quality in software development. As process more and more defines people and processes, how can you strive for better quality of releases?
-
Developing Microservices with Behavior Driven Development and Interface Oriented Design
These dependencies require well-defined and well-tested services. Behavior Driven Development (BDD) and Interface Oriented Design (IOD) help achieve this. BDD concentrates on the functionality of the services, which are specified with tests. IOD identifies contractual obligations (e.g. failure reporting) of the services.
-
Adopting Continuous Delivery at teamplay, Siemens Healthineers
Continuous Delivery is about working in a way that keeps the system in a releasable state throughout its development. This article describes how a large software development organization at Siemens Healthineers started the transformation towards Continuous Delivery. It describes the strategy and tactics used to gradually and safely change the development process in a regulated medical domain.
-
Is TDD a Form of OCD?
Developers are increasingly testing their own and each other's code. "Evaluation anxiety" is common psychological condition that is directly impacted by self-testing and team-testing. Are practices like TDD a defense mechanism to protect coders from criticism? And do emerging methods like Behavior Driven Development represents a more emotionally healthy approach to team evaluation?
-
Perspective on Architectural Fitness of Microservices
In this article we peel the onion of potential architectural fitness of microservices in the context of Master Data Management, and the challenges a microservices-based architecture may face when solving problem domains that require compute-intensive tasks, such as the calculation of expected losses on a portfolio of unsecured consumer credit.
-
Automated Journey Testing with Cascade
Starting with a brief history of software testing, we investigate Cascade, a new framework for testing “journeys”, eliminating overlapping coverage to produce fast unit tests.
-
Why and How to Test Logging
Logging and aggregation are crucial tools for today's complex, distributed systems. They provide rich insights which keep time to recover short. We must therefore make sure we test logging adequately.
-
Beyond Page Objects: Next Generation Test Automation with Serenity and the Screenplay Pattern
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.
-
Interview and Book Review: BDD In Action
"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.
-
*-Driven* do not change anything
Michał Bartyzel challenges the need to master a *Driven* approach to be Software Professional. These might be: DDD, TDD, BDD, MDD or other frameworks. He maintains that they may be responsible for cognitive biases rather than playing a supporting role for broader and deeper skills.
-
Metrics-Driven Development
In this article the author shares his thoughts and experience gathered while working together with DEV teams, trying to make sense of metrics. He introduces the practice of Metrics-Driven-Development: using metrics to drive the entire application development.
-
Virtual Panel: Code-to-Test Ratios, TDD and BDD
In the last couple of months several online discussions took place about test first or test last, code-to-test ratios or whether BDD is really just TDD. InfoQ asked the opinion of BDD and TDD experts.