Specification Pattern vs Spec in BDD
- by cadmium
I'm trying to explore Behavior Driven Design and Domain Driven Design. I'm getting that written specifications drive the tests in BDD, but also that business logic can be encapsulated using the specification pattern for re-use in domain objects and repositories, etc.
Are these basically the same concept just used in different ways, used in conjunction together, or am I completely confusing the concepts?
Please shed some light, if possible.