验收测试和功能测试之间的区别? [英] Difference between acceptance test and functional test?

查看:702
本文介绍了验收测试和功能测试之间的区别?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

验收测试和功能测试之间的真正区别是什么?

What is the real difference between acceptance tests and functional tests?

每一个的重点或目标是什么?我读过的每个地方都模棱两可.

What are the highlights or aims of each? Everywhere I read they are ambiguously similar.

推荐答案

在我的世界中,我们使用以下术语:

In my world, we use the terms as follows:

功能测试:这是验证活动;我们是否构建了可以正常工作的产品?该软件是否符合业务要求?

functional testing: This is a verification activity; did we build a correctly working product? Does the software meet the business requirements?

对于这种类型的测试,我们的测试用例涵盖了我们可以想到的所有可能的场景,即使该场景不太可能存在于现实世界中"也是如此.在进行此类测试时,我们旨在最大程度地覆盖代码.我们使用当时可以抓住的任何测试环境,只要可以使用,就不必具有生产"能力.

For this type of testing we have test cases that cover all the possible scenarios we can think of, even if that scenario is unlikely to exist "in the real world". When doing this type of testing, we aim for maximum code coverage. We use any test environment we can grab at the time, it doesn't have to be "production" caliber, so long as it's usable.

验收测试:这是一项验证活动;我们建立了正确的东西吗?这是客户真正需要的吗?

acceptance testing: This is a validation activity; did we build the right thing? Is this what the customer really needs?

通常与客户合作或由内部客户代理(产品负责人)完成此操作.对于此类测试,我们使用的测试用例涵盖了我们期望使用该软件的典型场景.此测试必须在类似于生产"的环境中,在与客户使用的硬件相同或接近的硬件上进行.这是我们测试不道德行为"的时候:

This is usually done in cooperation with the customer, or by an internal customer proxy (product owner). For this type of testing we use test cases that cover the typical scenarios under which we expect the software to be used. This test must be conducted in a "production-like" environment, on hardware that is the same as, or close to, what a customer will use. This is when we test our "ilities":

  • 可靠性,可用性:通过压力测试进行了验证.

  • Reliability, Availability: Validated via a stress test.

可伸缩性:通过负载测试进行验证.

Scalability: Validated via a load test.

可用性:通过对客户的检查和演示进行验证.用户界面是否根据自己的喜好进行了配置?我们是否在所有正确的位置放置了客户品牌?我们是否拥有他们要求的所有字段/屏幕?

Usability: Validated via an inspection and demonstration to the customer. Is the UI configured to their liking? Did we put the customer branding in all the right places? Do we have all the fields/screens they asked for?

安全性 (又名安全性",仅供参考):通过演示进行了验证.有时,客户会聘请外部公司进行安全审核和/或入侵测试.

Security (aka, Securability, just to fit in): Validated via demonstration. Sometimes a customer will hire an outside firm to do a security audit and/or intrusion testing.

可维护性:通过演示我们将如何交付软件更新/补丁进行验证.

Maintainability: Validated via demonstration of how we will deliver software updates/patches.

可配置性:通过演示客户如何修改系统以满足其需求进行验证.

Configurability: Validated via demonstration of how the customer can modify the system to suit their needs.

这绝不是标准,而且我不认为有标准"定义,如此处矛盾的答案所示.对于您的组织而言,最重要的是,您必须准确定义这些术语,并遵守它们.

This is by no means standard, and I don't think there is a "standard" definition, as the conflicting answers here demonstrate. The most important thing for your organization is that you define these terms precisely, and stick to them.

这篇关于验收测试和功能测试之间的区别?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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