出版時間:2011-3 出版社:電子工業(yè) 作者:(美)達斯廷//加勒特//高夫 頁數(shù):340
Tag標簽:無
內(nèi)容概要
本書講解什么是自動化測試,為什么要進行自動化測試,以及實施自動化測試過程中的各種方法和需要注意的問題?!蹲詣踊浖y試實施指南(英文版)》分為兩個部分,第一部分中作者以自身的經(jīng)驗詮釋了自動化測試的重要性以及好處;第二部分具體講解了自動化測試中的6個要點,包括需求收集、制定自動化測試策略、測試自動化軟件測試框架、持續(xù)跟蹤過程并調(diào)整、實施自動化測試過程以及恰當?shù)娜藛T安排。附錄中還給出了具體的自動化測試實?。
本書適合作為軟件測試自動化相關(guān)課程的雙語教材,也適合軟件測試人員、質(zhì)量評估人員、項目管理人員和軟件開發(fā)人員作為參考用書。
作者簡介
作者:(美國)達斯廷(Elfriede Dustin) (美國)加勒特(Thom Garrett) (美國)高夫(Bernie Gauf)Elfriede Dustin,Thom Garrett和Bernie Gauf工作作Innovative Defense Technologies(ID)公司,這家公司專門設(shè)計、開發(fā)和實現(xiàn)自動化軟件測試解決方案。Dustin領(lǐng)導IDT的自動化軟件測試研究工作,撰寫過多本關(guān)于軟件測試的圖書。Garrett在規(guī)劃、開發(fā)、測試和開發(fā)用于軍事和商業(yè)企業(yè)的復雜軟件系統(tǒng)方面有二十多年的經(jīng)驗。Gauf是IDT公司的總裁,他積極參與DOD關(guān)于新技術(shù)應用的顧問組,并在許多軟件測試峰會上做過演講。
書籍目錄
contents
foreword by admiral edmund p. giambastiani, jr
foreword by dr. william nylin, jr
preface
acknowledgments
about the authors
Ⅰ. what is automated software testing and why shoul we
automate?
1.what is effective automated software testing (ast)?
1.1 automated software testing definition
1.2 automated software testing recipes
1.3 advances in ast technologies
1.4 automating various software testing types
1.5 providing ast-based production support
1.6 automating standards assessments
2.why automate?
2.1 the challenges of testing software today
2.2 reducing the time and cost of software testing
2.3 impacting software quality
2.4 improvements to your software test program
3.the business case
3.1 definition of the business case
3.2 identifying the business needs
3.3 justifying automation in terms of cost and benefits
3.4 risks
3.5 other considerations
4.why automated software testing fails and pitfalls to avoid
4.1 r&d does not generally focus on automated or manual testing
efforts
4.2 ast myths and realities
4.3 lack of software development consideration for ast
4.4 the forest for the trees-not knowing which tool to pick
4.5 lack of automaton standards across tool vendors
4.6 lack of business case
Ⅱ.how to automate: top six keys for automation payoff
5.key 1: know your requirements
5.1 understand the ast support requirements
5.2 additional information in support of ast requirements
5.3 when information is not available
5.4 start implementing your requirements traceability
matrix(rtm)
……
contributing authors
index
章節(jié)摘錄
版權(quán)頁:插圖:Once a test has failed, the tester will usually have to perform some"focused" testing by modifying the original test scenario, if necessary, to determine the application's "breaking point," or the factors that cause or do not cause the system to break. During this exercise ,architectural knowledge of the SUT can be of great help to the tester. It will enable the test engineer to perform more useful and specific investigative testing, and perhaps allow him or her to skip additional superfluous and unrelated testing altogether, since knowledge of the underlying components allows him or her to determine eadditional information about the problem. For example, if the application encounters a connection problem with the database, then it is not necessary to attempt the operation with different data values.Instead, before testing can continue, the focus will be on resolving the connection issues.
編輯推薦
《自動化軟件測試實施指南(英文版)》:為AST構(gòu)建實際可行的商業(yè)案例,使用AST獲取主動權(quán)明確測試需求,并開發(fā)一個滿足這些需求的自動化策略構(gòu)建高效的測試環(huán)境,為該環(huán)境選擇正確的自動化工具和技術(shù)使用經(jīng)過證明的指標持續(xù)地跟蹤過程,并作出相應調(diào)整不管是測試專業(yè)人員、QA專家、項目經(jīng)理還是開發(fā)人員,《自動化軟件測試實施指南(英文版)》都會帶給你前所未有的有效測試,并使用AST改進整個開發(fā)生命周期。
圖書封面
圖書標簽Tags
無
評論、評分、閱讀與下載