掌握软件测试艺术第三版：实践与策略

1星需积分: 47 145 浏览量更新于2023-03-16 2 收藏 2.51MB PDF 举报

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

领优惠券(最高得80元）

《软件测试的艺术》第三版是Glenford J. Myers、Tom Baggett和Corey Sandler合著的一本经典著作，该书深入探讨了软件测试领域的艺术与科学。作为一部权威的专业书籍，它不仅介绍了软件测试的基础概念，还提供了实用的策略和方法，帮助读者提升测试技能，确保软件质量。此版本由John Wiley & Sons, Inc.出版，版权属于Word Association, Inc.，并且遵循1976年美国版权法的规定。本书的主要内容涵盖了以下几个方面： 1. **软件测试基础**：作者从理论角度出发，解释了软件测试的目的，包括识别错误、验证功能和性能以及评估软件可靠性。读者可以了解到软件测试的生命周期，包括测试计划、设计、执行和报告等阶段。 2. **测试方法与技术**：书中详细讨论了各种测试技术，如单元测试、集成测试、系统测试和验收测试，以及它们之间的关系和适用场景。同时，它还会涉及自动化测试、黑盒测试、白盒测试、灰盒测试等不同测试策略。 3. **测试工具和实践**：书中可能会介绍一些常用的测试工具，并提供如何选择和使用这些工具来提高测试效率和效果的建议。此外，书中可能会探讨敏捷开发环境下的测试适应性。 4. **缺陷管理**：章节可能涵盖如何有效地报告、跟踪和修复缺陷，以及通过度量和分析来改善测试过程和产品质量。 5. **测试人员的角色**：书中会强调测试团队在项目中的重要性，包括测试设计者、测试工程师和质量保证专家的角色定义，以及如何培养优秀的测试专业人才。 6. **测试创新与未来趋势**：第三版可能会更新最新的测试理念和技术，比如测试驱动开发（TDD）、持续集成（CI）和持续交付（CD）等现代软件开发实践中的角色。 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

www.it-ebooks.info

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

www.it-ebooks.info

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

www.it-ebooks.info

剩余253页未读，继续阅读

mmcatt

粉丝: 4
资源: 14

会员权益专享

掌握软件测试艺术第三版：实践与策略

软件测试 第三版

软件测试（第三版）

《软件测试技术基础教程》习题解答

软件测试-------三角形逻辑覆盖

软件测试-------三角形逻辑覆盖代码

软件测试80-20原则

全程软件测试第三版pdf

软件测试----路径覆盖

软件测试方法和技术第三版pdf

全程软件测试第三版朱少民

软件测试c语言测试三角形,软件测试-判断三角形形状路径白盒测试.docx

软件测试基础思维导图

软件测试打电话,如何有效测试手机通话测试 - fox的测试人生 - 51Testing软件测试网 51Testing软件测试网-软件测试人的精神家园...

java测试覆盖率_软件测试基础 - 测试覆盖率

软件测试的艺术第3版 pan csdn

glenford j.myers 软件测试艺术

软件测试自学全套教程

软件质量保证与测试-------自动化测试实验项目结论

软件测试自动化课堂笔记

会员权益专享

最新资源

软件测试第三版