A software development approach that extends TDD by writing tests in natural language that describe the expected behavior of the system from a user's perspective. Tests are written in a Given-When-Then format that stakeholders can understand.
Coined by Dan North in 2003 as an evolution of test-driven development. North wanted to address the confusion around 'what to test' by focusing on behavior rather than implementation, using the word 'behavior' from psychology to emphasize observable actions and outcomes.
Try Another Word