軟件測(cè)試

內(nèi)容概要

　　文藝復(fù)興以降，源遠(yuǎn)流長(zhǎng)的科學(xué)精神和逐步形成的學(xué)術(shù)規(guī)范，使西方國(guó)家在自然科學(xué)的各個(gè)領(lǐng)域取得了壟斷性的優(yōu)勢(shì)；也正是這樣的傳統(tǒng)，使美國(guó)在信息技術(shù)發(fā)展的六十多年間名家輩出、獨(dú)領(lǐng)風(fēng)騷。在商業(yè)化的進(jìn)程中，美國(guó)的產(chǎn)業(yè)界與教育界越來越緊密地結(jié)合，計(jì)算機(jī)學(xué)科中的許多泰山北斗同時(shí)身處科研和教學(xué)的最前線，由此而產(chǎn)生的經(jīng)典科學(xué)著作，不僅擘劃了研究的范疇，還揭示了學(xué)術(shù)的源變，既遵循學(xué)術(shù)規(guī)范，又自有學(xué)者個(gè)性，其價(jià)值并不會(huì)因年月的流逝而減退。
　　近年，在全球信息化大潮的推動(dòng)下，我國(guó)的計(jì)算機(jī)產(chǎn)業(yè)發(fā)展迅猛，對(duì)專業(yè)人才的需求日益迫切。這對(duì)計(jì)算機(jī)教育界和出版界都既是機(jī)遇，也是挑戰(zhàn)；而專業(yè)教材的建設(shè)在教育戰(zhàn)略上顯得舉足輕重。在我國(guó)信息技術(shù)發(fā)展時(shí)間較短的現(xiàn)狀下，美國(guó)等發(fā)達(dá)國(guó)家在其計(jì)算機(jī)科學(xué)發(fā)展的幾十年間積淀和發(fā)展的經(jīng)典教材仍有許多值得借鑒之處。因此，引進(jìn)一批國(guó)外優(yōu)秀計(jì)算機(jī)教材將對(duì)我國(guó)計(jì)算機(jī)教育事業(yè)的發(fā)展起到積極的推動(dòng)作用，也是與世界接軌、建設(shè)真正的世界一流大學(xué)的必由之路。
　　機(jī)械工業(yè)出版社華章公司較早意識(shí)到“出版要為教育服務(wù)”。自1998年開始，我們就將工作重點(diǎn)放在了遴選、移譯國(guó)外優(yōu)秀教材上。經(jīng)過多年的不懈努力，我們與pearson，mcgraw-hill，elsevier，mit，john
wiley & sons，cengage等世界著名出版公司建立了良好的合作關(guān)系，從他們現(xiàn)有的數(shù)百種教材中甄選出andrew
s. tanenbaum，bjarne stroustrup，brain w. kernighan，dennis
ritchie，jim gray，afred v. aho，john e. hopcroft，jeffrey d.
ullman，abraham silberschatz，william stallings，donald e. knuth，john
l. hennessy，larry l.
peterson等大師名家的一批經(jīng)典作品，以“計(jì)算機(jī)科學(xué)叢書”為總稱出版，供讀者學(xué)習(xí)、研究及珍藏。大理石紋理的封面，也正體現(xiàn)了這套叢書的品位和格調(diào)。
　　
“計(jì)算機(jī)科學(xué)叢書”的出版工作得到了國(guó)內(nèi)外學(xué)者的鼎力襄助，國(guó)內(nèi)的專家不僅提供了中肯的選題指導(dǎo)，還不辭勞苦地?fù)?dān)任了翻譯和審校的工作；而原書的作者也相當(dāng)關(guān)注其作品在中國(guó)的傳播，有的還專程為其書的中譯本作序。迄今，“計(jì)算機(jī)科學(xué)叢書”已經(jīng)出版了近兩百個(gè)品種，這些書籍在讀者中樹立了良好的口碑，并被許多高校采用為正式教材和參考書籍。其影印版“經(jīng)典原版書庫(kù)”作為姊妹篇也被越來越多實(shí)施雙語教學(xué)的學(xué)校所采用。

作者簡(jiǎn)介

作者：（愛爾蘭）布朗（Stephen Brown） （愛爾蘭）Joe Timoney （愛爾蘭）Tom Lysaght 葉德仕 （Deshi Ye）

書籍目錄

前言
1 introduction
　1．1 the software industry
　1．2 software testing and quality
　1．3 errors．faults and failures
　　1．3．1 software faults
　　1．3．2 software failures
　　1．3．3 need for testing
　1．4 the role of sdecifications
　1．5 overview of testing
　　1．5．1 testing in the development process
　　1．5．2 test automation
　1．6 the theory of testing
　　1．6．1 exhaustive testing example
　　1．6．2 implications
　1．7 when to finish testing
　1．8 notes on book structure
2 principles of software testing
　.2．1 dynamic and static verification
　　2．1．1 static verification
　　2．1．2 dynamic verification
　2．2 black-box and white．box testing
　　2．2．1 errors of“omission”and“commission”
　2．3 test approaches
　　2．3．1 black-box testing
　　2．3．2 white-box testing
　　2．3．3 fault insertion
　2．4 test activities
　　2．4．1 analysis outputs
　　2．4．2 test cases
　　2．4．3 test data
　　2．4．4 test code for test proceduresl
　2．5 analysis of software specifications
　　2．5．1 parameters
　　2．5．2 parameter ranges
　　2．5．3 equivalence partitions
　　2．5．4 boundary values
　　2．5．5 combinations of values
　　2．5．6 sequences of values
　2．6 analysis of software components
　　2．6．1 control flow graphs
　　2．6．2 decisions and conditions
　　2．6．3 paths
　　2．6．4 data-flow testing
　　2．6．5 ranking
　2．7 analysis of targets for fault insertion
　　2．7．1 offutt’s 5 sufficient mutations
　2．8 test artefacts
3 unit testing
　3．1 introduction
　3．2 usage
　3．3 black-box techniques
　　3．3．1 equivalence partitioning(ep)
　　3．3．2 boundary value analysis fbval
　　3．3．3 testing combinations of inputs(ci)
　　3．3．4 testing sequences of inputs(si)or state
　　3．3．5 random input data fridl
　　3．3．6 error guessing fegl
　3．4 white．box techniques
　　3．4．1 statement coverage fscl
　　3．4．2 branch coverage fbcl
　　3．4．3 condition coverage fccl
　　3．4．4 decision condition coverage fdccl
　　3．4．5 multiple condition coverage(mcc)
　　3．4．6 path coverage fpci
　　3．4．7 d—u pair coverage(dup)
　　3．5 fault insertion
　3．5．1 strong mutation testing(smt)
4 unit testing examples
5 static v_erification
6 testing object-oriented software
7 integration and system testing
8 software test automation
9 testing in the software process
10 advanced testing issues
a terminology
b exercises
select bibliography 　　　　
　　

章節(jié)摘錄

版權(quán)頁(yè)：   插圖：   7.1.7 Conclusion Overall,when it comes to selecting an integration testing strategy for a softwareapplication a number of things should be considered.These include the number of stubsand drivers to be produced,the location of the critical modules in the system,whichlayers will be available for testing,and what order the layers are to be implementedin.Integration testing is difficult as it does require synchronization between testers anddevelopers in the production,combination and testing of modules.Also,faults foundduring integration testing can be harder to resolve,and finally,if design features need tobe changed they may result in conflicts with the customer. 7.2 System Testing This means testing of the system as a whole and is almost invariably done using Blackbox tests.System testing can be broken down into a number of categories that mayor may not be carried out on the product,as their necessity depends on the type ofapplication it is.These are listed and explained below.It will be noticed that at timessome of these testing activities overlap in terms of what they measure.This reflects thatnot all tests may be applicable to the one product. 7.2.1 System Test Categories Conformance Testing Used to verify that the system conforms to a set of publishedstandards.Many standards will have a published suite of conformance tests,orhave a selected authority to run these tests.This is particularly important forcommunications software,as software system must correctly inter-operate withother implementations. Documentation Testing Used to verify that the documentation(in printed form,online,help,or prompts)is sufficient for the software to be installed and operatedefficiently.Typically a full installation is performed,and then the different systemfunctions are executed,exactly as documented.Responses are checked against thedocumented responses.Ergonomic Testing Used to verify the ease-of-use of the system.This can be eitherautomated(verifying font sizes,information placement on the screen,use of colours,or the speed of progress by users of different experience levels),or manual(basedon feedback forms completed by users).

編輯推薦

《軟件測(cè)試:原理與實(shí)踐(英文版)》主要是面向軟件測(cè)試的本科課程來設(shè)計(jì)相關(guān)內(nèi)容，但書中講述的理論和技術(shù)輔以許多實(shí)際的例子來說明，這些實(shí)用的內(nèi)容對(duì)于軟件專業(yè)人員也很有吸引力。因?yàn)檐浖y(cè)試是現(xiàn)代軟件工程項(xiàng)目管理的一個(gè)非常關(guān)鍵的要素，其重要性日漸顯現(xiàn)，正在引起軟件產(chǎn)業(yè)乃至IT產(chǎn)業(yè)的充分重視……

圖書封面

圖書標(biāo)簽Tags

無

評(píng)論、評(píng)分、閱讀與下載

---

    軟件測(cè)試 PDF格式下載

---