{"product_id":"testing-computer-software-paperback-softback-9780471358466","title":"Testing Computer Software (Paperback \/ softback) 9780471358466","description":"\u003cfont face=\"Georgia\"\u003e\r\n\u003cp\u003e\u003cfont size=\"6\"\u003eTesting Computer Software\u003c\/font\u003e\u003cbr\u003e\r\n\r\n\r\n\r\n\r\n\r\n\u003c\/p\u003e\n\u003cp\u003e\u003cfont size=\"4\"\u003eCem Kaner (Author), Jack Falk (Author), Hung Q. Nguyen (Author)\u003c\/font\u003e\u003c\/p\u003e\r\n\r\n\u003cp\u003e\u003cfont size=\"3\"\u003e9780471358466, Wiley\u003c\/font\u003e\u003c\/p\u003e\r\n\r\n\u003cp\u003e\u003cfont size=\"3\"\u003ePaperback \/ softback, published 22 April 1999\u003c\/font\u003e\u003c\/p\u003e\r\n\r\n\u003cp\u003e\u003cfont size=\"3\"\u003e496 pages\u003cbr\u003e23.4 x 18.8 x 2.5 cm, 0.83 kg\u003c\/font\u003e\u003c\/p\u003e\r\n\r\n\r\n\r\n\u003cp align=\"justify\"\u003e\u003cem\u003e\u003cfont size=\"3\"\u003e\"I enjoyed reading Testing computer software. The text contains numerous highlights Offering practical advice, authoritative figures you can cite to customers and higher management, and entertaining anecdotes to share with coworkers Although some sections need updating, I still think it is a valuable training and reference source for software testers, managers, and developers.\" --Diomidis Spinellis; IEEE software magazine (May \/June 2001))\u003cbr\u003e \"Deep insight and a great deal of experience is contained in this book\" (Database \u0026amp; Network Journal, Vol 30\/5 2000)\u003c\/font\u003e\u003c\/em\u003e\u003c\/p\u003e\r\n\r\n\u003cp align=\"justify\"\u003e\u003cstrong\u003e\u003cfont size=\"3\"\u003eDies ist die 2. Auflage eines herausragenden und äußerst erfolgreichen Softwaretitels, der auch von Amazon besonders empfohlen wird. Früher herausgegeben von VNR Computer Library, ist dieses Buch jetzt bei Wiley erhältlich. Zuverlässige Computer-Software ist der Schlüssel zum Erfolg aller IT-Unternehmen und -systeme. Jedoch ist es unmöglich erfolgreiche und zuverlässige Software herzustellen, ohne daß diese ein umfangreiches Testverfahren durchläuft. Und genau um diese Testverfahren geht es hier. Cem Kaner, anerkannter Experte auf diesem Gebiet, hat mit diesem Buch einen Leitfaden verfaßt, der von unschätzbarem Wert ist für ALLE: Für Studenten, die sich um eine Stelle als Software-Tester bewerben, für erfahrene Programmierer, die Fehler schnell aufdecken müssen oder mit einer Armada von Testern kommunizieren müssen und für Projekt- und Test-Manager, die eine Vielzahl von Leuten, Fristen und Erwartungen jedes einzelnen Softwareprojekts unter einen Hut kriegen müssen. Außerdem ist dieses Buch eine große Hilfe für alle, die ein Betriebssystem für den Privatgebrauch erworben haben, das nicht ihren Erwartungen entspricht. Der Erfolg dieses Buches beruht auf seiner Realitätsnähe und Praxisbezogenheit: Qualität und Zuverlässigkeit von Software am modernen Arbeitsplatz. (y08\/99)\u003cbr\u003e\u003c\/font\u003e\u003c\/strong\u003e\u003c\/p\u003e\r\n\r\n\u003cp\u003e\u003cfont size=\"3\"\u003e\u003cp\u003ePreface xiii\u003c\/p\u003e \u003cp\u003eNotes on the book’s structure and layout xvii\u003c\/p\u003e \u003cp\u003eAcknowledgments xxi\u003c\/p\u003e \u003cp\u003e\u003cb\u003eSECTION 1—FUNDAMENTALS\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e\u003cb\u003e1. An example test series 1\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003eThe first cycle of testing 1\u003c\/p\u003e \u003cp\u003eThe second cycle of testing 11\u003c\/p\u003e \u003cp\u003eWhat will happen in later cycles of testing 16\u003c\/p\u003e \u003cp\u003e\u003cb\u003e2. The objectives and limits of testing 17\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003eYou can’t test a program completely 17\u003c\/p\u003e \u003cp\u003eThe tester’s objective: Program verification? 23\u003c\/p\u003e \u003cp\u003eSo, why test? 25\u003c\/p\u003e \u003cp\u003e\u003cb\u003e3. Test types and their place in the software development process 27\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003eOverview of the software development stages 30\u003c\/p\u003e \u003cp\u003ePlanning stages 32\u003c\/p\u003e \u003cp\u003eTesting during the planning stages 33\u003c\/p\u003e \u003cp\u003eDesign stages 35\u003c\/p\u003e \u003cp\u003eTesting during the design stages 39\u003c\/p\u003e \u003cp\u003eGlass box code testing is part of the coding stage 41\u003c\/p\u003e \u003cp\u003eRegression testing 49\u003c\/p\u003e \u003cp\u003eBlack box testing 50\u003c\/p\u003e \u003cp\u003eMaintenance 57\u003c\/p\u003e \u003cp\u003e\u003cb\u003e4. Software errors 59\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003eQuality 59\u003c\/p\u003e \u003cp\u003eWhat is a software error? 60\u003c\/p\u003e \u003cp\u003eCategories of software errors 60\u003c\/p\u003e \u003cp\u003e\u003cb\u003e5. Reporting and analyzing bugs 65\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003eWrite Problem Reports immediately 66\u003c\/p\u003e \u003cp\u003eContent of the Problem Report 66\u003c\/p\u003e \u003cp\u003eCharacteristics of the Problem Report 74\u003c\/p\u003e \u003cp\u003eAnalysis of a reproducible bug 76\u003c\/p\u003e \u003cp\u003eTactics for analyzing a reproducible bug 79\u003c\/p\u003e \u003cp\u003eMaking a bug reproducible 82\u003c\/p\u003e \u003cp\u003e\u003cb\u003eSECTION 2—SPECIFIC TESTING SKILLS\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e\u003cb\u003e6. The problem tracking system 87\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003eThe prime objective of a problem tracking system 90\u003c\/p\u003e \u003cp\u003eThe tasks of the system 90\u003c\/p\u003e \u003cp\u003eProblem tracking overview 90\u003c\/p\u003e \u003cp\u003eThe users of the tracking system 97\u003c\/p\u003e \u003cp\u003eMechanics of the database 106\u003c\/p\u003e \u003cp\u003eFurther thoughts on problem reporting 115\u003c\/p\u003e \u003cp\u003eGlossary 121\u003c\/p\u003e \u003cp\u003e\u003cb\u003e7. Test case design 123\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003eCharacteristics of a good test 124\u003c\/p\u003e \u003cp\u003eEquivalence classes and boundary values 125\u003c\/p\u003e \u003cp\u003eVisible state transitions 132\u003c\/p\u003e \u003cp\u003eRace conditions and other time dependencies 133\u003c\/p\u003e \u003cp\u003eLoad testing 134\u003c\/p\u003e \u003cp\u003eError guessing 135\u003c\/p\u003e \u003cp\u003eFunction equivalence testing: automation, sensitivity analysis \u0026amp; random input 135\u003c\/p\u003e \u003cp\u003eRegression testing: checking whether a bug fix worked 139\u003c\/p\u003e \u003cp\u003eRegression testing: the standard battery of tests 140\u003c\/p\u003e \u003cp\u003eExecuting the tests 141\u003c\/p\u003e \u003cp\u003e\u003cb\u003e8. Testing printers (and other devices) 143\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003eSome general issues in configuration testing 144\u003c\/p\u003e \u003cp\u003ePrinter testing 146\u003c\/p\u003e \u003cp\u003e\u003cb\u003e9. Localization testing 169\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003eWas the base code changed? 170\u003c\/p\u003e \u003cp\u003eWork with someone fluent in the language 170\u003c\/p\u003e \u003cp\u003eIs the text independent from the code? 171\u003c\/p\u003e \u003cp\u003eTranslated text expands 171\u003c\/p\u003e \u003cp\u003eCharacter sets 171\u003c\/p\u003e \u003cp\u003eKeyboards 172\u003c\/p\u003e \u003cp\u003eText filters 172\u003c\/p\u003e \u003cp\u003eLoading, saving, importing, and exporting high and low ASCII 173\u003c\/p\u003e \u003cp\u003eOperating system language 173\u003c\/p\u003e \u003cp\u003eHot keys 173\u003c\/p\u003e \u003cp\u003eGarbled in translation 173\u003c\/p\u003e \u003cp\u003eError message identifiers 174\u003c\/p\u003e \u003cp\u003eHyphenation rules 174\u003c\/p\u003e \u003cp\u003eSpelling rules 174\u003c\/p\u003e \u003cp\u003eSorting rules 174\u003c\/p\u003e \u003cp\u003eUppercase and lowercase conversion 174\u003c\/p\u003e \u003cp\u003eUnderscoring rules 174\u003c\/p\u003e \u003cp\u003ePrinters 175\u003c\/p\u003e \u003cp\u003eSizes of paper 175\u003c\/p\u003e \u003cp\u003eCPU’s and video 175\u003c\/p\u003e \u003cp\u003eRodents 175\u003c\/p\u003e \u003cp\u003eData formats and setup options 175\u003c\/p\u003e \u003cp\u003eRulers and measurements 176\u003c\/p\u003e \u003cp\u003eCulture-bound graphics 176\u003c\/p\u003e \u003cp\u003eCulture-bound output 176\u003c\/p\u003e \u003cp\u003eEuropean product compatibility 176\u003c\/p\u003e \u003cp\u003eMemory availability 176\u003c\/p\u003e \u003cp\u003eDo GUIs solve the problem? 177\u003c\/p\u003e \u003cp\u003eAutomated testing 177\u003c\/p\u003e \u003cp\u003e\u003cb\u003e10. Testing user manuals 179\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003eEffective documentation 179\u003c\/p\u003e \u003cp\u003eThe documentation tester’s objectives 180\u003c\/p\u003e \u003cp\u003eHow testing documentation contributes to software reliability 181\u003c\/p\u003e \u003cp\u003eBecome the technical editor 182\u003c\/p\u003e \u003cp\u003eWorking with the manual through its development stages 183\u003c\/p\u003e \u003cp\u003eOnline help 188\u003c\/p\u003e \u003cp\u003e\u003cb\u003e11. Testing tools 189\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003eFundamental tools 189\u003c\/p\u003e \u003cp\u003eAutomated acceptance and regression tests 191\u003c\/p\u003e \u003cp\u003eStandards 197\u003c\/p\u003e \u003cp\u003eTranslucent-box testing 200\u003c\/p\u003e \u003cp\u003e\u003cb\u003e12. Test planning and test documentation 203\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003eThe overall objective of the test plan: product or tool? 204\u003c\/p\u003e \u003cp\u003eDetailed objectives of test planning and documentation 205\u003c\/p\u003e \u003cp\u003eWhat types of tests to cover in test planning documents 210\u003c\/p\u003e \u003cp\u003eA strategy for developing components of test planning documents 213\u003c\/p\u003e \u003cp\u003eComponents of test planning documents 217\u003c\/p\u003e \u003cp\u003eDocumenting test materials 242\u003c\/p\u003e \u003cp\u003eA closing thought 253\u003c\/p\u003e \u003cp\u003e\u003cb\u003eSECTION 3—MANAGING TESTING PROJECTS AND GROUPS\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003e\u003cb\u003e13. Tying it together 255\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003eSoftware development tradeoffs 257\u003c\/p\u003e \u003cp\u003eSoftware development models 258\u003c\/p\u003e \u003cp\u003eQuality-related costs 264\u003c\/p\u003e \u003cp\u003eThe development time line 266\u003c\/p\u003e \u003cp\u003eProduct design 267\u003c\/p\u003e \u003cp\u003eFragments coded: first functionality 274\u003c\/p\u003e \u003cp\u003eAlmost alpha 275\u003c\/p\u003e \u003cp\u003eAlpha 277\u003c\/p\u003e \u003cp\u003ePre-beta 286\u003c\/p\u003e \u003cp\u003eBeta 286\u003c\/p\u003e \u003cp\u003eUser interface (UI) freeze 293\u003c\/p\u003e \u003cp\u003ePre-final 295\u003c\/p\u003e \u003cp\u003eFinal integrity testing 299\u003c\/p\u003e \u003cp\u003eRelease 301\u003c\/p\u003e \u003cp\u003eProject post-mortems 301\u003c\/p\u003e \u003cp\u003e\u003cb\u003e14. Legal consequences of defective software 303\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003eBreach of contract 305\u003c\/p\u003e \u003cp\u003eTorts: lawsuits involving fault 317\u003c\/p\u003e \u003cp\u003eWhistle blowing 340\u003c\/p\u003e \u003cp\u003e\u003cb\u003e15. Managing a testing group 343\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003eManaging a testing group 344\u003c\/p\u003e \u003cp\u003eThe role of the testing group 345\u003c\/p\u003e \u003cp\u003eA test group is not an unmixed blessing 349\u003c\/p\u003e \u003cp\u003eAn alternative? Independent test agencies 350\u003c\/p\u003e \u003cp\u003eScheduling tips 352\u003c\/p\u003e \u003cp\u003eYour staff 359\u003c\/p\u003e \u003cp\u003eAppendix: common software errors 363\u003c\/p\u003e \u003cp\u003eUser interface errors 375\u003c\/p\u003e \u003cp\u003eError handling 396\u003c\/p\u003e \u003cp\u003eBoundary-related errors 399\u003c\/p\u003e \u003cp\u003eCalculation errors 401\u003c\/p\u003e \u003cp\u003eInitial and later states 403\u003c\/p\u003e \u003cp\u003eControl flow' errors 406\u003c\/p\u003e \u003cp\u003eErrors in handling or interpreting data 416\u003c\/p\u003e \u003cp\u003eRace conditions 421\u003c\/p\u003e \u003cp\u003eLoad conditions 423\u003c\/p\u003e \u003cp\u003eHardware 427\u003c\/p\u003e \u003cp\u003eSource, version, and ID control 430\u003c\/p\u003e \u003cp\u003eTesting errors 432\u003c\/p\u003e \u003cp\u003eReferences 437\u003c\/p\u003e \u003cp\u003eIndex 451\u003c\/p\u003e \u003cp\u003eAbout the Authors 480\u003c\/p\u003e\u003c\/font\u003e\u003c\/p\u003e\r\n\r\n\u003cp\u003e\u003cfont size=\"3\"\u003eSubject Areas: Electronics \u0026amp; communications engineering [\u003ca title=\"See our other books on Electronics \u0026amp; communications engineering\" href=\"https:\/\/freshlyprintedbooks.co.uk\/search?q=%22Electronics%20\u0026amp;%20communications%20engineering%20%5BTJ%5D%22\"\u003eTJ\u003c\/a\u003e]\u003c\/font\u003e\u003c\/p\u003e\r\n\r\n\r\n\u003c\/font\u003e","brand":"Wiley","offers":[{"title":"Brand New","offer_id":52293393645848,"sku":"9780471358466","price":56.76,"currency_code":"GBP","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0730\/2037\/5320\/files\/9780471358466.jpg?v=1781639556","url":"https:\/\/freshlyprintedbooks.co.uk\/products\/testing-computer-software-paperback-softback-9780471358466","provider":"Freshly Printed Books","version":"1.0","type":"link"}