单元测试

单元测试包括测试最小的代码单元，通常是函数或方法。单元测试主要由单元/方法/函数的开发人员完成，因为他们了解函数的核心。开发人员的主要目标是通过单元测试来覆盖代码。

它有一个限制，即某些函数不能通过单元测试进行测试。即使在成功完成所有单元测试之后;它不保证产品的正确操作。相同的函数可以在系统的少数部分中使用，而单元测试仅为一种用途而编写。

功能测试

It is a type of Black Box testing where testing will be done on the functional aspects of a product without looking into the code. Functional testing is mostly done by a dedicated Software tester. It will include positive, negative and BVA techniques using un standardized data for testing the specified functionality of product. Test coverage is conducted in an improved manner by functional tests than by unit tests. It uses application GUI for testing, so it’s easier to determine what exactly a specific part of the interface is responsible for rather to determine what a code is function responsible for.

我们可以很简单地说:

黑盒:用户界面测试，比如功能测试 白盒:类似单元测试的代码测试

点击这里阅读更多。

我认为它是这样的:单元测试确定代码执行了您希望代码执行的操作(例如，您想要添加参数A和b，实际上是将它们相加，而不是减去它们)，功能测试测试所有代码一起工作以获得正确的结果，因此您希望代码执行的操作实际上在系统中获得了正确的结果。

单元测试

单元测试包括测试最小的代码单元，通常是函数或方法。单元测试主要由单元/方法/函数的开发人员完成，因为他们了解函数的核心。开发人员的主要目标是通过单元测试来覆盖代码。

它有一个限制，即某些函数不能通过单元测试进行测试。即使在成功完成所有单元测试之后;它不保证产品的正确操作。相同的函数可以在系统的少数部分中使用，而单元测试仅为一种用途而编写。

功能测试

It is a type of Black Box testing where testing will be done on the functional aspects of a product without looking into the code. Functional testing is mostly done by a dedicated Software tester. It will include positive, negative and BVA techniques using un standardized data for testing the specified functionality of product. Test coverage is conducted in an improved manner by functional tests than by unit tests. It uses application GUI for testing, so it’s easier to determine what exactly a specific part of the interface is responsible for rather to determine what a code is function responsible for.

单元测试告诉开发人员代码的工作是正确的;功能测试告诉开发人员代码正在做正确的事情。

你可以在单元测试与功能测试中阅读更多内容

单元测试和功能测试在现实生活中的类比可以描述如下:

Many times the development of a system is likened to the building of a house. While this analogy isn't quite correct, we can extend it for the purposes of understanding the difference between unit and functional tests. Unit testing is analogous to a building inspector visiting a house's construction site. He is focused on the various internal systems of the house, the foundation, framing, electrical, plumbing, and so on. He ensures (tests) that the parts of the house will work correctly and safely, that is, meet the building code. Functional tests in this scenario are analogous to the homeowner visiting this same construction site. He assumes that the internal systems will behave appropriately, that the building inspector is performing his task. The homeowner is focused on what it will be like to live in this house. He is concerned with how the house looks, are the various rooms a comfortable size, does the house fit the family's needs, are the windows in a good spot to catch the morning sun. The homeowner is performing functional tests on the house. He has the user's perspective. The building inspector is performing unit tests on the house. He has the builder's perspective.

总结一下，

单元测试是从程序员的角度编写的。它们用于确保类的特定方法(或单元)执行一组特定的任务。

功能测试是从用户的角度编写的。它们确保系统按照用户的期望运行。

TLDR:

回答这个问题:单元测试是功能测试的一个子类型。

有两大类:功能测试和非功能测试。我发现的最好的(非详尽的)例子是这个(来源:www.inflectra.com):

(1)单元测试:测试小段代码(函数/方法)。它可以被认为是(白盒)功能测试。

当功能放在一起时，你创建了一个模块=一个独立的部分，可能有一个可以测试的用户界面(模块测试)。一旦你有了至少两个独立的模块，然后你把它们粘在一起，然后就来了:

(2)集成测试:当你把两个或多个(子)模块或(子)系统放在一起，看看它们是否能很好地发挥作用。

然后你整合了第3个模块，然后是第4和第5个模块，按照你或你的团队认为合适的顺序，一旦所有的拼图碎片放在一起，就完成了

(3)系统测试:对软件进行整体测试。这差不多就是“所有部件的集成测试”。

如果没问题，那就来吧

(4)验收测试:我们实际构建了客户要求的东西吗?当然，验收测试应该在整个生命周期中进行，而不仅仅是在最后一个阶段，在这个阶段，你意识到客户想要一辆跑车，而你建造了一辆货车。