blocks|key|1713594|text|根本不是写它们。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1713595|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

blocks|key|1713378|text|在一次测试中测试太多。我的单元测试通常具有更多的集成测试特征，因为它不会将自己限制在测试方法中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1713379|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Testing too much in one test. My unit tests often take on more of the character of integration tests by not confining themselves to the method under test.

blocks|key|1498254|text|编写与他们正在测试的代码过于耦合的测试。尤其是当我依赖于语义耦合和我假设为类工作的东西时，这一点尤其正确。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1498255|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Writing tests that are too coupled to the code they are testing. This is especially true where I am relying on semantic coupling and things that I just assume to work for the class.

blocks|key|1713329|text|依赖于一些实现细节，这些细节不是测试功能的一部分，可能会在以后的开发中发生变化。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1713330|有时，这些假设太难排除，或者太令人望而却步，无法考虑，而且是可变的。|1713331|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Relying on some implementation detail which is not part of the tested functionality and that might change later on in the development. 
Sometimes these assumptions are just too hard to factor out or too prohibitive to take into consideration and being variable.

blocks|key|1713358|text|缺乏覆盖率--我很少测试我第一次通过时应该测试的所有案例。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1713359|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Lack of coverage -- I rarely test all the cases I should on my first pass.

blocks|key|1713558|text|忘记在双重比较中加入舍入误差容限可能是我最大的、也是最令人恼火的错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1713559|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Forgetting to put in the rounding error allowance in double comparison is probably my biggest and most annoying mistake.

blocks|key|1498410|text|只使用一些随机值进行测试，而不是使用等价分区和边界值分析进行测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1498411|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Testing using just some random values instead of including testing with equivalence partitioning and boundary value analysis.

blocks|key|1713611|text|而不是先写它们(例如，不走测试驱动路线)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1713612|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Not writing them first (ie. not going the Test Driven route)

blocks|key|1498572|text|通过不使用模拟对象或框架来使两个集成点紧密耦合。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1498573|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Making two integration points tightly coupled by not using a mock object or framework.

blocks|key|1713687|text|没有得到足够整洁和整洁的测试夹具-所以编写测试比它应该的更难。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1713688|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Not getting the test fixtures neat and tidy enough - so writing the tests is harder than it should be.

blocks|key|1713728|text|编写既不是单元测试(仅测试特定方法)也不是验收测试(从用户角度进行测试)的测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1713729|我发现，在一次测试中测试3-4层代码，而不是基于商业人士理解的概念，通常会导致测试成为维护的负担，并使人们感到失望，并因自动化测试而关闭。|1713730|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Writing tests that are neither unit tests( testing only the specific method) nor acceptance tests( testing from user's perspective). 

I find that tests that testing 3-4 layers of code in one test that is not grounded at concepts that biz people understand, usually lead to tests that are a burden to maintain and make people get disappointed and turned off by automated testing.

blocks|key|1498354|text|省略了一些小细节(例如，单元测试中没有任何字母的十六进制到十进制函数……)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1498355|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Leaving out some small detail (e.g. a hex to dec function where the unit test didn't have any letters in it...)

blocks|key|1498381|text|嗯，我有时会错过输出测试C#属性，测试甚至不会运行:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1498382|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Well, I sometimes miss out putting out the [Test] C# attribute, and the test doesn't even get run :)

blocks|key|1498583|text|http://msdn.microsoft.com/en-us/magazine/cc163665.aspx|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1498584|entityMap|0|LINK|mutability|MUTABLE|url^0|0|1I|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@$A|L|B|M|1|N]]|C|$]]|$1|D|3|-4|5|6|7|O|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|4]]]]

<a href="http://msdn.microsoft.com/en-us/magazine/cc163665.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/magazine/cc163665.aspx</a>

blocks|key|1498661|text|只有部分代码覆盖率的单元测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1498662|测试成功了，所以我感觉很好。事情正在进行中。我转移到其他事情上。结果发现有一个未经测试的角落案例。|1498663|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Unit tests with only partial code coverage.

The tests succeed, so I'm feeling good. Things are working. I move on to something else. Turns out there's an untested corner case.

blocks|key|1498678|text|测试依赖于您碰巧使用的操作系统的怪癖，或先前测试的无意副作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1498679|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Tests that depend on a quirk of the OS you happen to be on, or an unintentional side effect of a previous test.

What is the one most common mistake you make while writing unit tests? Coupling? Lack of cohesion? Try to test too much functionality at once? Not testing enough functionality? 

Post some example code if you have an example of that mistake

What is the most common mistake you make while writing unit tests?

在编写单元测试时，您最常犯的错误是什么？耦合？缺乏凝聚力？试着一次测试太多的功能？没有测试足够的功能？如果你有一个错误的例子，请发布一些例子代码

问在编写单元测试时最常犯的错误是什么？
EN

回答 16

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在编写单元测试时最常犯的错误是什么？EN

回答 16

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在编写单元测试时最常犯的错误是什么？
EN