《软件测试的艺术》英文原版：权威指南

测试工具

软件测试

需积分: 5 20 浏览量更新于2024-06-26 收藏 5.22MB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

"《软件测试的艺术》是软件测试领域的一本经典著作，由Glenford J. Myers、Tom Badgett和Corey Sandler合著的第三版。本书详细探讨了软件测试的各种理论和实践方法，旨在帮助读者理解并提升在软件开发过程中的测试技能。" 在软件开发过程中，测试是确保产品质量的关键环节。《软件测试的艺术》一书深入讲解了这个领域的核心概念和技术，包括以下几个方面： 1. 测试基础：书中介绍了软件测试的基础理论，包括为什么进行测试，测试的目标，以及如何设计有效的测试用例。它强调了测试在软件生命周期中的重要性，并提供了测试策略和计划制定的指导。 2. 测试方法论：作者探讨了不同的测试方法，如黑盒测试、白盒测试和灰盒测试，以及它们各自的适用场景。这些方法论有助于测试人员根据项目需求选择合适的测试策略。 3. 缺陷管理：书中详细阐述了缺陷的发现、记录、跟踪和修复过程，以及如何通过缺陷分析改进软件质量。缺陷管理是软件测试中的关键组成部分，对于提高软件产品的可靠性至关重要。 4. 自动化测试：随着技术的发展，自动化测试已成为现代软件测试的重要工具。书中涵盖了自动化测试的基本原理，包括脚本编写、测试框架的选择和实施，以及如何有效地集成自动化测试到持续集成流程中。 5. 性能和压力测试：性能测试用于评估软件在特定负载下的表现，而压力测试则关注系统在极端条件下的稳定性。书中介绍了如何设计和执行这些类型的测试，以确保软件在高并发或大规模使用时的稳定性和性能。 6. 回归测试与持续测试：随着软件迭代更新，回归测试确保新功能不会破坏现有功能。书中讨论了如何有效地进行回归测试，以及如何构建持续测试环境，以实现测试的自动化和持续集成。 7. 风险与测试优先级：书中还涉及如何识别和评估软件开发中的风险，以及如何基于这些风险来确定测试的优先级，确保关键问题能得到及时解决。此外，本书还强调了测试文档的重要性，如测试计划、测试报告和测试总结，这些都是软件测试过程中不可或缺的部分。同时，书中也提到了测试人员的职业发展和团队协作的技巧，这对于提升整个团队的测试能力具有实际指导意义。《软件测试的艺术》是一本全面且深入的指南，适合软件测试工程师、开发人员、项目经理等专业人士阅读，无论是初学者还是经验丰富的从业者，都能从中受益匪浅，提升自身的软件测试水平。

资源详情

资源推荐

C01 08/11/2011 11:29:16 Page 2

Software testing is easier, too, in some ways, because the array of soft-

ware and operating systems is much more sophisticated than in the past,

providing i ntri nsic, well-te sted routines that can be incorporated into

applications without the need for a programmer to develop them from

scratch. Graphical User Interfaces (GUIs), for example, can be built from a

development language’s libraries, and since they are preprogrammed ob-

jects that have been debugged and tested previously, the need for testing

them as part of a custom application is much reduced.

And, despite the plethora of software testing tomes available on the

market today, many developers seem to have an attitude that is counter

to extensive testing. Better development tools, pretested GUIs, and the

pressure of tight deadl ines in an ever more complex development envi-

ronment can lead to avoidance o f all but the most obvious te sting

protocols. Whereas low-level impacts of bugs may only inconvenie nce

the end user, the worst impacts can result in large ﬁnancial loses, o r e ven

cause harm to people. The procedures in this book can help designers,

developers, and project m anagers better understand the value of compre-

hensive testing, and provide guidelines to help them achieve required

testing goals.

Software testing is a process, or a series of processes, designed to make

sure computer code does what it was designed to do and, conversely, that it

does not do anything unintended. Software should be predictable and con-

sistent, presenting no surprises to users. In this book, we will look at many

approaches to achieving this goal.

Now, before we start the book, we’d like you to take a short exam. We

want you to write a set of test cases—speciﬁc sets of data—to test properly

a relatively simple program. Create a set of test data for the program—data

the program must handle correctly to be considered a successful program.

Here’s a description of the program:

The program reads three integer values from an input dialog. The

three values represent the lengths of the sides of a triangle. The pro-

gram displays a message that states whether the triangle is scalene,

isosceles, or equilateral.

Remember that a scalene triangle is one where no two sides are equal,

whereas an isosceles triangle h as two equal sides, and a n equilatera l

triangle has three sides of equal length. Moreover, the angles opposite the

2 The Art of Software Testing

C01 08/11/2011 11:29:16 Page 3

equal sides in an isosceles triangle also are equal (it also follows that the

sidesoppositeequalanglesinatriangleareequal),andallanglesinan

equilateral triangle are equal.

Evaluate your set of test cases by using it to a nswer the followi ng

questions. Give yourself one point for each yes answer.

1. Do you have a test c ase that represents a valid scalene triangle?

(Note that test cases such as 1, 2, 3 and 2, 5, 10 do not warrant a yes

answer because a triangle having these dimensions is not valid.)

2. Do you have a test case that represents a valid equilateral triangle?

3. Do you have a test case that represents a valid isosceles triangle?

(Note that a test case representing 2, 2, 4 would not count because it

is not a valid triangle.)

4. Do you have at least three test cases that represent valid isosceles

triangles such that you have tried all three permutations of two equal

sides (such as, 3, 3, 4; 3, 4, 3; and 4, 3, 3)?

5. Do you have a test case in which one side has a zero value?

6. Do you have a test case in which one side has a negative value?

7. Do you have a test case with three integers greater than zero such that

the sum of two of the numbers is equal to the third? (That is, if the

program said that 1, 2, 3 represents a scalene triangle, it would contain

abug.)

8. Do you have at least three test cases in category 7 such that you have

tried all three permutations where the length of one side is equal to

the sum of the lengths of the other two sides (e.g., 1, 2, 3; 1, 3, 2; and

3, 1, 2)?

9. Do you have a test case with three integers greater than zero such that

the sum of two of the numbers is less than the third (such as 1, 2, 4 or

12, 15, 30)?

10. Do you have at least three test cases in category 9 such that you have

tried all three permutations (e.g., 1, 2, 4; 1, 4, 2; and 4, 1, 2)?

11. Do you have a test case in which all sides are zero (0, 0, 0)?

12. Do you have at least one test case specifying noninteger values

(such as 2.5, 3.5, 5.5)?

13. Do you have at least one test case specifying the wrong number of

values (two rather than three integers, for example)?

14. For each test case did you specify the expected output from the

program in addition to the input values?

A Self-Assessment Test 3

C02 08/25/2011 11:54:11 Page 6

These deﬁnitions are upside down.

When you test a program, you want to add some value to it. Adding

value through testing means raising the quality or reliability of the program.

Raising the reliability of the program means ﬁnding and removing errors.

Therefore, don’t test a program to show that it works; rather, start with

the assumption that the program contai ns errors (a valid assumption for

almost any program) and then test the program to ﬁnd as many of the

errors as possible.

Thus, a more appropriate deﬁnition is this:

Testing is the process of executing a program with the intent of ﬁnd-

ing errors.

Although this may sound like a game of subtle semantics, it’s really an

important distinction. Understanding the true deﬁnition of software test-

ing can make a profound difference in the success of your efforts.

Human be ings tend to be hi ghly goal-orient ed , and establis hin g the

proper goal has an important psychological effect on them. If our goal is to

demonstrate that a program has no errors, then we will be steered sub-

consciously toward this goal; that is, we tend to select test data that have a

low probability of causing the program to fail. On the other hand, i f our

goal is to demonstrate that a program has errors, our test data will have a

higher probability of ﬁnding errors. The latter approach will add more

value to the program than the former.

This deﬁnition of testing has myriad implications, many of which are

scattered throughout this book. For instance, it implies that testing is a

destructive, even sadistic, process, which explains why most people ﬁnd it

difﬁcult. That may go against our grain; with good fortune, most of us have

a constructive, rather than a destructive, outlook on life. Most people are

inclined toward making objects rather than ripping them apart. The deﬁni-

tion also has implications for how test cases (test data) should be designed,

and who should and who should not test a given program.

Another way of reinfor cing the proper deﬁnition of testing is to analyze

the use of the words ‘‘successful’’ and ‘‘unsuccessful’’—in particular, their use

by project managers in categorizing the results of test cases. Most project

managers refer to a test case that did not ﬁnd an error a ‘ ‘successful test run,’’

whereas a test that discovers a new error is usually called ‘‘unsuccessful.’ ’

Once again, this is upside down. ‘‘Unsuccessful’’ denotes something un-

desirable or disappointing. To our way of thinking, a well-constructed and

6 The Art of Software Testing

剩余253页未读，继续阅读

纯手打_

粉丝: 0
资源: 5

《软件测试的艺术》英文原版：权威指南

软件测试艺术 英文原版

软件测试艺术《英文版》

软件测试艺术--英文版

Table 3: Performance comparison with state-of-the-art approaches on all datasets

art-template安装后没有express-art-template模块

the art of electronics英文原版

GANprintR: Improved Fakes and Evaluation of the State of the Art in Face Manipulation Detection

pycinrad 和 py-art

angelicax-art

有没有transformer的使用链接

1. "Object Segmentation using Superpixel-based Region Merging" by Zhang, Z., et al. (2015)

express-art-template

The Art of Unit Testing (With Examples in .NET) 介绍

officehome-art-resnet50-noft.mat

curl -H "X-JFrog-Art-Api:<API_KEY>" -T <PATH_TO_FILE>

explain software architecture of android

最新资源

软件测试艺术英文原版