规格型号与规格在BDD [英] Specification Pattern vs Spec in BDD

查看:228
本文介绍了规格型号与规格在BDD的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在尝试探索行为驱动设计和域驱动设计。我得到了书面规范驱动BDD中的测试,但也可以使用规范模式封装业务逻辑,以便在域对象和存储库等中重复使用。

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.

推荐答案

BDD或上下文规范是以测试方式进行单元测试的一种风格。 DDD是由埃里克·埃文斯(Eric Evans)创造的一个术语,它在构建软件系统时基本上重新引入了适当的设计模式。如果您想要在上下文规范样式中进行测试第一次开发,那么请参阅链接。从BDD的角度来看,如果您真的想使用埃里克·埃文斯(Eric Evans)的书中描述的模式来设计软件系统,那么您会发现一些很好的资源 here

BDD or context specification is a style of writing unit tests in a test first manner. DDD is a term coined by Eric Evans that basically re-introduces appropriate design patterns when you are constructing software systems. If you are wanting to do test first development in a context specification style then see this link. From a BDD standpoint there are lots of resources out there if you really want to design your software systems using the patterns described in Eric Evans' book you will find some good resources here

这篇关于规格型号与规格在BDD的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆