精华帖 (0) :: 良好帖 (0) :: 新手帖 (0) :: 隐藏帖 (0)
|
|
---|---|
作者 | 正文 |
发表时间:2007-08-13
http://www.china-pub.com/computers/common/info.asp?id=19120 [url]http://www.amazon.com/exec/obidos/ASIN /0131016490/qid=1097646507/sr=2-3/ ref=pd_ka_b_2_3/103-9945153-2808617[/url] It's very weird to read: "Tests in TDD is different from unit tests" For me, I think unit tests is same with tests in TDD except in TDD you need write tests first, but they are unit tests, aren't they? Or the difference indicate different feeling? What's your thoughts? 声明:ITeye文章版权属于作者,受法律保护。没有作者书面许可不得转载。
推荐链接
|
|
返回顶楼 | |
发表时间:2007-08-13
大概是说unit比TDD要多吧
没有临界点也没有非正常输入之类的东东,代码量会少一些吧 主要是有些unit test不能自动测试 |
|
返回顶楼 | |
发表时间:2007-08-14
抛出异常的爱 写道 大概是说unit比TDD要多吧
Do you mean the number of unit tests are more than TDD's? I don't think so, also in my company all unit tests be run automatically, that's why we write unit tests.没有临界点也没有非正常输入之类的东东,代码量会少一些吧 主要是有些unit test不能自动测试 IMO: 1. tests in TDD: define your functionalities of software, driven your product code 2. unit tests: verify functionalities of product code 3. I think they are same, but you will get different feeling on them |
|
返回顶楼 | |
发表时间:2007-08-14
我认为TDD的测试叫增涨型,可修改的测试(测试也是有可能会被改动的)
而另一种测试应该与白盒测试相似。。。 包括:语句覆盖、判定覆盖、条件覆盖、判定/条件覆盖、条件组合覆盖和路径覆盖发现错误的能力 白盒测试传说是靠一些工具完成的。 |
|
返回顶楼 | |
发表时间:2007-08-14
测试驱动是否和持续集成有关联?
|
|
返回顶楼 | |
发表时间:2007-08-14
yiding_he 写道 测试驱动是否和持续集成有关联? Yes, I must agree TDD often has relationship with Continue Product Integration(CPI), in my pratice, CPI is focus on product level, i.e. I can get product kit everyday, and when I run CPI testing, it will auto build all demos of product and run them(often client/server). But I want to say I don't run CPI everyday except release month.
IMO, I think TDD has closer relationship with nightly build and cruisecontrol building. |
|
返回顶楼 | |
发表时间:2007-08-14
抛出异常的爱 写道 我认为TDD的测试叫增涨型,可修改的测试(测试也是有可能会被改动的)
I agree with you 抛出异常的爱 写道 而另一种测试应该与白盒测试相似。。。 包括:语句覆盖、判定覆盖、条件覆盖、判定/条件覆盖、条件组合覆盖和路径覆盖发现错误的能力 白盒测试传说是靠一些工具完成的。 can't agree with you all - I often write unit tests, and use code coverage tool like jcoverage or clover to find unit testing quality, so that means you should write test first before using some tools to help you - for system testing, I use silktest/TPTP/win runner, that's the same with what you said |
|
返回顶楼 | |
发表时间:2007-08-14
How to TDD based on how you create unit test.
The difference is that different people has different test cases. |
|
返回顶楼 | |
发表时间:2007-08-14
怎么就非得用英文呢?
是因为英文爽还是不会安装中文输入法呢? 进入正题。。。。 TDD这个东东,我想TW的高手已经用精炼的一句话表达的十分清楚: 引用 把你的需求用测试描述出来 这就是TDD和普通的测试的区别。 |
|
返回顶楼 | |
发表时间:2007-08-14
用英语出于对lz的礼貌。
这句话说得很对,你我的不同点是进一步讲,对同一问题 不同的人有不同的问题分解。 |
|
返回顶楼 | |