Agile testing tutorials and how to content : Test-Driven Development (TDD), Behavior-Driven Development (BDD) and other agile approaches for software testing.
Once you start to get good at Test-Driven Development (TDD), you begin to learn the nuances of the discipline such as the fact that tests and code grow in very opposite directions. As the tests get more specific, the code gets more generic.
Let’s have a close look into the Red-Green-Refactor cycle and understand the subtleties of each step. When we go down the rabbit hole of Test Driven Design (TDD), we sometimes take too big steps leading us to many failed tests we just can bring back to green without writing a lot of code. We need to take a step back and take the shrinking potion of baby steps again.
This presentation looks at the chasm-crossing potential of Test-Driven Development (TDD) and some related technologies. The aim is that you will still be able to get a good job in 2024.
Behaviour Driven Development (BDD) is an Agile practice that aim at merging requirements documentation and software testing. What makes this technique different is that it engages Stakeholders from start to finish of a project. This is done by writing Specifications by Example in collaboration with all Stakeholders.
Test-Driven Development (TDD) has been tattered, torn, twisted, stood on its head, and pounded into an pulp of techno-fetishism. TDD was a game-changer, but the focus in the interceding years has shifted from technique to tools and TDD has been devolving into a lost art.
The increasing adoption of Agile project management frameworks like Scrum and short iteration schedule has a deep impact on the place of software testing and the activity of QA people. In this blog post, Chris Burns tries to answer the often-asked question: “what does QA do on the first day of a Scrum sprint?”
In theory everyone on an Agile team is responsible for software testing, but in practice this is rarely the case. Learn how to make quality a team sport in Scrum teams.