blocks|key|1922521|text|一般来说，测试可能是...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1922522|1922523|unit+test测试您软件的单个子组件，而不依赖于其他classes|unordered-list-item|offset|length|1922524|integration+test，这是测试两个独立系统之间的连接的测试。用于验证system|1922525|功能的集成capability|1922526|acceptance+test|1922527|1922528|...and还有一些我很可能暂时忘记的东西。|1922529|然而，在TDD中，您在创建软件时主要关注单元测试。|1922530|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Unit_testing|1|http://en.wikipedia.org/wiki/Integration_testing|2|http://en.wikipedia.org/wiki/Acceptance_testing^0|0|0|0|9|0|0|0|G|1|0|0|0|F|2|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|16|8|@]|9|@$F|17|G|18|1|19]]|A|$]]|$1|H|3|I|5|E|7|1A|8|@]|9|@$F|1B|G|1C|1|1D]]|A|$]]|$1|J|3|K|5|6|7|1E|8|@]|9|@]|A|$]]|$1|L|3|M|5|E|7|1F|8|@]|9|@$F|1G|G|1H|1|1I]]|A|$]]|$1|N|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1K|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1L|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]|10|$5|V|W|X|A|$Y|11]]|12|$5|V|W|X|A|$Y|13]]]]

In general the test may be...

<ul>
<li><a href="http://en.wikipedia.org/wiki/Unit_testing" rel="noreferrer">unit test</a> which tests an individual subcomponent of your software without any external dependencies to other classes</li>
<li><a href="http://en.wikipedia.org/wiki/Integration_testing" rel="noreferrer">integration test</a> which are tests that test the connection between two separate systems, ie. their integration capability</li>
<li><a href="http://en.wikipedia.org/wiki/Acceptance_testing" rel="noreferrer">acceptance test</a> for validating the functionality of the system</li>
</ul>

...and some others I've most likely temporarily forgotten for now.

In TDD, however, you're mostly focusing on the unit tests when creating your software.

blocks|key|621795|text|它完全是单元测试驱动的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|621796|基本思想是首先编写单元测试，然后执行通过测试所需的绝对最少量的工作。|621797|然后编写更多的测试来覆盖更多的需求，并实现更多的测试以使其通过。|621798|这是一个迭代的过程，先是测试编写，然后是代码编写。|621799|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

It's entirely Unit Test driven.

The basic idea is to write the unit tests first, and then do the absolute minimum amount of work necessary to pass the tests.

Then write more tests to cover more of the requirements, and implement a bit more to make it pass.

It's an iterative process, with cycles of test writing, and then code writing.

blocks|key|2120311|text|下面是Unclebob写的几篇好文章|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2120312|Three+rules+of+TDD|offset|length|2120313|TDD+with+Acceptance+and+Unit+tests|2120314|entityMap|0|LINK|mutability|MUTABLE|url|http://butunclebob.com/ArticleS.UncleBob.TheThreeRulesOfTdd|1|http://blog.objectmentor.com/articles/2007/10/17/tdd-with-acceptance-tests-and-unit-tests^0|0|0|I|0|0|0|Y|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

Here are a couple of good articles by Unclebob

<a href="http://butunclebob.com/ArticleS.UncleBob.TheThreeRulesOfTdd" rel="nofollow noreferrer">Three rules of TDD</a>

<a href="http://blog.objectmentor.com/articles/2007/10/17/tdd-with-acceptance-tests-and-unit-tests" rel="nofollow noreferrer">TDD with Acceptance and Unit tests</a>

blocks|key|1922537|text|我会说它是关于单元测试和代码覆盖率的。它是关于发布没有错误的代码，并能够在未来轻松地进行更改。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1922538|请参阅Bob大叔的words+of+wisdom。|offset|length|1922539|entityMap|0|LINK|mutability|MUTABLE|url|http://www.objectmentor.com/omSolutions/dialogs/practice_ttd.html^0|0|9|F|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

I would say it is about unit testing and code coverage. It is about shipping bugless code and being able to make changes easily in the future.

See Uncle Bob's <a href="http://www.objectmentor.com/omSolutions/dialogs/practice_ttd.html" rel="nofollow noreferrer">words of wisdom</a>.

blocks|key|2120484|text|我如何使用它，它是面向单元测试的。假设我想要一个整型数平方的方法，我写这个方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2120485|int+square(int+x)+{+return+null;+}|code-block|syntax|javascript|2120486|然后编写一些测试，比如：|2120487|[Test]
TestSquare()+
{
Assert.AreEqual(square(0),0);
Assert.AreEqual(square(1),1);
Assert.AreEqual(square(10),100);
Assert.AreEqual(square(-1),1);
Assert.AreEqual(square(-10),100);
....
}|2120488|好吧，也许square是一个不好的例子:-)|2120489|在每种情况下，我都测试预期的行为和所有的边界值，比如maxint、zero和null-value+(记住，你也可以测试错误)，并确保测试失败(这并不难:-))然后我继续处理这个函数，直到它工作。|2120490|所以:首先，一个单元测试失败了，它覆盖了你想要覆盖的东西，然后是方法。|2120491|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

How I use it, it's unit testing oriented. Suppose I want a method that square ints I write this method : 

<pre><code>int square(int x) { return null; }
</code></pre>

and then write some tests like : 

<pre><code>[Test]
TestSquare() 
{
Assert.AreEqual(square(0),0);
Assert.AreEqual(square(1),1);
Assert.AreEqual(square(10),100);
Assert.AreEqual(square(-1),1);
Assert.AreEqual(square(-10),100);
....
}
</code></pre>

Ok, maybe square is a bad example :-) 

In each case I test expected behaviour and all borderline vals like maxint and zero and null-value (remember you can test on errors too) and see to it the test fails (which isn't hard :-)) then I keep working on the function until it works. 

So : first a unit test that fails an covers what you want it to cover, then the method.

blocks|key|2120524|text|通常，"TDD“中的单元测试不应该涉及任何IO。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2120525|事实上，如果您编写不产生副作用的对象(I/O几乎总是副作用！)，并根据方法的返回值或对传入对象的接口的调用来定义类的行为，那么您将获得更高的效率。|2120526|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|$]]

Generally, unit tests in "TDD" shouldn't involve any IO at all.

In fact, you'll have a ton more effectiveness if you write objects that do not create side effects (I/O is almost always, if not always, a side effect!), and define your the behavior of your class either in terms of return values of methods, or calls made to interfaces that have been passed into the object.

blocks|key|1922618|text|我只想给出我对这个话题的看法，这可能有助于以不同的方式更多地理解TDD。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1922619|TDD是一种首先依赖于测试的设计方法。因为您问到测试结果如何，所以我会这样回答：|1922620|如果你想构建一个应用程序，你知道你想要构建什么的目的，并且你通常知道当你完成的时候，或者在你需要测试它的过程中，例如检查你通过代码检查创建的变量的值，或者快速地放置一个按钮，你可以点击这个按钮，然后执行一部分代码，并弹出一个对话框，显示操作的结果等等。|1922621|另一方面，TDD改变了您的思维方式，我将指出其中一种方式。通常，您只需要依赖开发环境(如visual+studio+)在编码和编译时检测错误，并且在您的头脑中的某个地方，您知道需求，只是通过按钮和弹出窗口或代码检查来编码和测试。我称之为SDDD+(语法调试驱动开发)。但是，当你在做TDD时，是一种“语义调试驱动的开发”，因为你首先通过测试(以及更动态和可重复的白板版本)写下你对应用程序的想法/目标，这些测试测试你的应用程序的逻辑(或“语义”)，当你有一个语义错误时，即使你的应用程序通过了语法错误(在编译时)，它也会失败。|1922622|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I just want to give my view on the topic which may help to understand TDD a bit more in a different way.

TDD is a design method that relies in testing first. because you asked about how the test is, ill go like this: 

If you want to build an application, you know the purpose of what you want to build and you know generally that when you are done, or along the way you need to test it e.g check the values of variables you create by code inspection, of quickly drop a button that you can click on and will execute a part of code and pop up a dialog to show the result of the operation etc. 

on the other hand TDD changes your mindset and i'll point out one of such ways. commonly , you just rely on the development environment like visual studio to detect errors as you code and compile and somewhere in your head, you know the requirement and just coding and testing via button and pop ups or code inspection. I call this style SDDD (Syntax debugging driven development ).
but when you are doing TDD, is a "semantic debugging driven development " because you write down your thoughts/ goals of your application first by using tests (which and a more dynamic and repeatable version of a white board) which tests the logic (or "semantic") of your application and fails whenever you have a semantic error even if you application passes syntax error (upon compilation).

blocks|key|622118|text|顺便说一句，尽管我说过“你知道你想要构建的东西的目的”，但在实践中，你可能不知道或不知道构建应用程序所需的所有信息，因为TDD会迫使你首先编写测试，所以你不得不在开发的非常早期阶段询问更多关于应用程序功能的问题，而不是构建很多东西，结果发现你编写的很多东西并不是必需的(或者至少现在不需要)。你真的可以避免浪费宝贵的时间在TDD上(即使它最初可能不是这样的)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|622119|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|$]]

by the way even though i said "you know the purpose of what you want to build ..", in practice you may not know or have all the information required to build the application , since TDD kind of forces you to write tests first, you are compelled to ask more questions about the functioning of the application at a very early stage of development rather than building a lot only to find out that a lot of what you have written is not required (or at lets not at the moment). you can really avoid wasting your precious time with TDD (even though it may not feel like that initially)

I've been learning what TDD is, and one question that comes to mind is what exactly is the "test". For example, do you call the webservice and then build the code to make it work? or is it more unit testing oriented?

Test Driven Development - What exactly is the test?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我一直在学习TDD是什么，我脑海中浮现的一个问题是，到底什么是“测试”。例如，您是否调用you服务，然后构建代码以使其工作？或者它更多地面向单元测试？

问测试驱动开发--测试到底是什么？
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问测试驱动开发--测试到底是什么？EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问测试驱动开发--测试到底是什么？
EN