《軟件工程-實(shí)踐者的研究方法》chapter-14-cn-軟件測試策略課件

1、These slides are designed to accompany Software Engineering: A Practitioners Approach, 7/e (McGraw-Hill, 2009). Slides copyright 2009 by Roger Pressman.1第十四章軟件測試策略Slide Set to accompanySoftware Engineering: A Practitioners Approach, 7/e by Roger S. PressmanSlides copyright 1996, 2001, 2005, 2009 by

2、Roger S. PressmanFor non-profit educational use onlyMay be reproduced ONLY for student use at the university level when used in conjunction with Software Engineering: A Practitioners Approach, 7/e. Any other reproduction or use is prohibited without the express written permission of the author.All c

3、opyright information MUST appear if these slides are posted on a website for student use.These slides are designed to aThese slides are designed to accompany Software Engineering: A Practitioners Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 2軟件測試測試是在程序發(fā)布給最終用戶之前，執(zhí)行程序以發(fā)現(xiàn)錯(cuò)

4、誤的過程。 .These slides are designed to aThese slides are designed to accompany Software Engineering: A Practitioners Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 3測試展示了錯(cuò)誤需求一致性性能質(zhì)量These slides are designed to aThese slides are designed to accompany Software Engineering: A P

5、ractitioners Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 4測試的策略性方法為完成有效的測試，軟件團(tuán)隊(duì)?wèi)?yīng)該進(jìn)行有效的、正式的技術(shù)評審。通過評審，許多錯(cuò)誤可以在測試開始之前排除。測試開始于構(gòu)件層，然后向外“延伸”到整個(gè)基于計(jì)算機(jī)系統(tǒng)的集成。 不同的測試技術(shù)適用于不同的時(shí)間點(diǎn)。測試由軟件開發(fā)人員和（對大型項(xiàng)目而言）獨(dú)立的測試組執(zhí)行。測試和調(diào)試是不同的活動(dòng)，但任何測試策略中都必須包括調(diào)試。These slides are designed to aThese slides are d

6、esigned to accompany Software Engineering: A Practitioners Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 5驗(yàn)證與確認(rèn)(V & V)驗(yàn)證是指確保軟件正確地實(shí)現(xiàn)某一特定功能的一系列活動(dòng)。確認(rèn)則指的是確保開發(fā)的軟件可追溯到用戶需求的另外一系列活動(dòng)。BOE81用另一種方式說明了這兩者的區(qū)別：驗(yàn)證：我們在正確地構(gòu)造產(chǎn)品嗎？確認(rèn)：我們在構(gòu)造正確的產(chǎn)品嗎？These slides are designed to aThese slides are

7、 designed to accompany Software Engineering: A Practitioners Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 6由誰來測試軟件？開發(fā)者獨(dú)立的測試人員Understands the system but, will test gentlyand, is driven by deliveryMust learn about the system,but, will attempt to break itand, is driven by

8、qualityThese slides are designed to aThese slides are designed to accompany Software Engineering: A Practitioners Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 7測試策略系統(tǒng)工程分析模型設(shè)計(jì)模型編碼單元測試集成測試確認(rèn)測試系統(tǒng)測試These slides are designed to aThese slides are designed to accompany Softwar

9、e Engineering: A Practitioners Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 8測試策略測試從“小規(guī)模”開始，進(jìn)展到“大規(guī)?！?。傳統(tǒng)軟件測試關(guān)注測試單個(gè)構(gòu)件或相關(guān)的一小組構(gòu)件構(gòu)件集成測試面向?qū)ο筌浖臏y試測試目標(biāo)就是在現(xiàn)實(shí)的時(shí)間范圍內(nèi)利用可控的工作量盡可能多地找到錯(cuò)誤。對于面向?qū)ο筌浖?，盡管這個(gè)基本目標(biāo)是不變的，但面向?qū)ο筌浖谋举|(zhì)特征改變了測試策略和測試戰(zhàn)術(shù)。These slides are designed to aThese slides are desi

10、gned to accompany Software Engineering: A Practitioners Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 9Strategic Issues早在開始測試之前，就要以量化的方式規(guī)定產(chǎn)品需求。明確地陳述測試目標(biāo)了解軟件的用戶并為每類用戶建立用戶輪廓。建立強(qiáng)調(diào)”快速周期測試“的測試計(jì)劃。建立能夠測試自身的“健壯”軟件測試之前，利用有效的正式技術(shù)評審作為過濾器。實(shí)施正式技術(shù)評審以評估測試策略和測試用例本身。為測試過程建立一種持續(xù)的改進(jìn)方法。Thes

11、e slides are designed to aThese slides are designed to accompany Software Engineering: A Practitioners Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 10單元測試測試模塊測試用例結(jié)果軟件工程師These slides are designed to aThese slides are designed to accompany Software Engineering: A Practiti

12、oners Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 11單元測試接口局部數(shù)據(jù)結(jié)構(gòu)邊界條件獨(dú)立路徑錯(cuò)誤處理路徑測試模塊測試用例These slides are designed to aThese slides are designed to accompany Software Engineering: A Practitioners Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 1

13、2單元測試環(huán)境被測模塊樁模塊樁模塊驅(qū)動(dòng)程序結(jié)果接口局部數(shù)據(jù)結(jié)構(gòu)邊界條件獨(dú)立路徑錯(cuò)誤處理路徑測試用例These slides are designed to aThese slides are designed to accompany Software Engineering: A Practitioners Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 13集成測試策略O(shè)ptions:the “big bang” approachan incremental construction st

14、rategyThese slides are designed to aThese slides are designed to accompany Software Engineering: A Practitioners Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 14自頂向下集成top module is tested with stubsstubs are replaced one at a time, depth firstas new modules are integrate

15、d, some subset of tests is re-runABCDEFGThese slides are designed to aThese slides are designed to accompany Software Engineering: A Practitioners Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 15自底向上集成drivers are replaced one at a time, depth firstworker modules are grou

16、ped into builds and integratedABCDEFGclusterThese slides are designed to aThese slides are designed to accompany Software Engineering: A Practitioners Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 16混合方式測試Top modules aretested with stubsWorker modules are grouped into bu

17、ilds and integratedABCDEFGclusterThese slides are designed to aThese slides are designed to accompany Software Engineering: A Practitioners Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 17回歸測試回歸測試是重新執(zhí)行已進(jìn)行測試的某個(gè)子集，以確保變更沒有傳播不期望的副作用。軟件發(fā)生變更時(shí)，軟件配置的某些方面（程序、文檔或支持?jǐn)?shù)據(jù)）也發(fā)生變更?；貧w測試有助于

18、保證變更（由于測試或其他原因）不引入無意識行為或額外的錯(cuò)誤。回歸測試可以手工進(jìn)行，方法是重新執(zhí)行所有測試用例的子集，或者利用捕捉、回放工具自動(dòng)進(jìn)行。These slides are designed to aThese slides are designed to accompany Software Engineering: A Practitioners Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 18Smoke TestingA common approach for creatin

19、g “daily builds” for product softwareSmoke testing steps:Software components that have been translated into code are integrated into a “build.” A build includes all data files, libraries, reusable modules, and engineered components that are required to implement one or more product functions.A serie

20、s of tests is designed to expose errors that will keep the build from properly performing its function. The intent should be to uncover “show stopper” errors that have the highest likelihood of throwing the software project behind schedule.The build is integrated with other builds and the entire pro

21、duct (in its current form) is smoke tested daily. The integration approach may be top down or bottom up.These slides are designed to aThese slides are designed to accompany Software Engineering: A Practitioners Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 19冒煙測試一種常用的集成測

22、試方法本質(zhì)上冒煙測試方法包括下列活動(dòng):將已經(jīng)轉(zhuǎn)換為代碼的軟件構(gòu)件集成到構(gòu)建中。設(shè)計(jì)一系列測試以暴露影響構(gòu)建正確完成其功能的錯(cuò)誤。每天將該構(gòu)建與其他構(gòu)建及整個(gè)軟件產(chǎn)品集成起來進(jìn)行冒煙測試。These slides are designed to aThese slides are designed to accompany Software Engineering: A Practitioners Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 20面向?qū)ο筌浖臏y試測試策略基于線程的測試，集成

23、響應(yīng)系統(tǒng)的一個(gè)輸入或事件所需的一組類。每個(gè)線程單獨(dú)地集成和測試。應(yīng)用回歸測試以確保沒有副效應(yīng)產(chǎn)生?；谑褂玫臏y試，通過測試很少使用服務(wù)類(如果有的話)的那些類(稱之為獨(dú)立類)開始構(gòu)造系統(tǒng)，面向?qū)ο筌浖念悳y試等同于傳統(tǒng)軟件的單元測試。不同的是傳統(tǒng)軟件的單元測試側(cè)重于模塊的算法細(xì)節(jié)和穿過模塊接口的數(shù)據(jù)，面向?qū)ο筌浖念悳y試是由封裝在該類中的操作和類的狀態(tài)行為驅(qū)動(dòng)的。These slides are designed to aThese slides are designed to accompany Software Engineering: A Practitioners Approach,

24、7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 21Broadening the View of “Testing”It can be argued that the review of OO analysis and design models is especially useful because the same semantic constructs (e.g., classes, attributes, operations, messages) appear at the analysis, des

25、ign, and code level. Therefore, a problem in the definition of class attributes that is uncovered during analysis will circumvent side effects that might occur if the problem were not discovered until design or code (or even the next iteration of analysis). These slides are designed to aThese slides

26、 are designed to accompany Software Engineering: A Practitioners Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 22Testing the CRC Model1. Revisit the CRC model and the object-relationship model.2. Inspect the description of each CRC index card to determine if a delegated

27、responsibility is part of the collaborators definition.3. Invert the connection to ensure that each collaborator that is asked for service is receiving requests from a reasonable source.4. Using the inverted connections examined in step 3, determine whether other classes might be required or whether

28、 responsibilities are properly grouped among the classes.5. Determine whether widely requested responsibilities might be combined into a single responsibility.6. Steps 1 to 5 are applied iteratively to each class and through each evolution of the analysis model.These slides are designed to aThese sl

29、ides are designed to accompany Software Engineering: A Practitioners Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 23高階測試確認(rèn)測試關(guān)注軟件需求系統(tǒng)測試關(guān)注系統(tǒng)集成Alpha/Beta 測試關(guān)注用戶使用恢復(fù)測試通過各種方式強(qiáng)制地讓系統(tǒng)發(fā)生故障，并驗(yàn)證其能適當(dāng)恢復(fù)安全測試驗(yàn)證建立在系統(tǒng)內(nèi)的保護(hù)機(jī)制是否能夠?qū)嶋H保護(hù)系統(tǒng)不受非法入侵壓力測試要求以非正常的數(shù)量、頻率或容量的方式執(zhí)行系統(tǒng)性能測試測試軟件在集成環(huán)境中的運(yùn)行性能The

30、se slides are designed to aThese slides are designed to accompany Software Engineering: A Practitioners Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 24調(diào)試：診斷的過程These slides are designed to aThese slides are designed to accompany Software Engineering: A Practitioners Appr

31、oach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 25診斷過程These slides are designed to aThese slides are designed to accompany Software Engineering: A Practitioners Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 26調(diào)試工作確定問題原因所花費(fèi)的時(shí)間糾正錯(cuò)誤和回歸測試需要的時(shí)間These sli

32、des are designed to aThese slides are designed to accompany Software Engineering: A Practitioners Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 27問題& 線索問題線索癥狀與原因出現(xiàn)的地方可能相隔很遠(yuǎn)；癥狀可能在另一個(gè)錯(cuò)誤被改正時(shí)(暫時(shí))消失癥狀實(shí)際上可能是由非錯(cuò)誤因素引起的；癥狀可能是由不易追蹤的人為錯(cuò)誤引起的；癥狀可能是由計(jì)時(shí)問題而不是處理問題引起的；癥狀可能時(shí)有時(shí)無；These slides are designed to aThese slides are designed to accompany Software Engineering: A Practitioners Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 28Bugs帶來的后果damagemildannoyingdisturbingseriousextremecatastrophicinfectiousBug TypeBug Categories: function-r