Agile testing tutorials and how to content : Test-Driven Development (TDD), Behavior-Driven Development (BDD) and other agile approaches for software testing.
Context Driven Testing can be defined by a is a set of values about software testing that recommends a continuous and creative assessment of the software testing activities based on the current knowledge about the situation and the value of the tests for the organization.
Software testing is an activity that has often been placed at the end of the software development life cycle, something that you did if there were some time left before the project deadline. In his book ” Scrum Shortcuts without Cutting Corners”, Ilan Goldstein explains that the software testers should be active since the beginning of the project.
Behaviour Driven Development (BDD) is an Agile software development process where behavioural specifications are expressed in a specific language that can be validated by a automated testing tool. RSpec is an open source a BDD tool for Ruby programmers. The Better Specs web site aims to collect the best practices about BDD with RSpec.
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.
Copyright © 2009-2025 Software Testing Magazine by Martinig & Associates