Effective Software Testing. (Record no. 25563)
[ view plain ]
| 000 -LEADER | |
|---|---|
| fixed length control field | 04683nam a22003253i 4500 |
| 001 - CONTROL NUMBER | |
| control field | EBC5125983 |
| 003 - CONTROL NUMBER IDENTIFIER | |
| control field | MiAaPQ |
| 005 - DATE AND TIME OF LATEST TRANSACTION | |
| control field | 20190104162501.0 |
| 006 - FIXED-LENGTH DATA ELEMENTS--ADDITIONAL MATERIAL CHARACTERISTICS--GENERAL INFORMATION | |
| fixed length control field | m o d | |
| 007 - PHYSICAL DESCRIPTION FIXED FIELD--GENERAL INFORMATION | |
| fixed length control field | cr cnu|||||||| |
| 008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION | |
| fixed length control field | 181231s2002 xx o ||||0 eng d |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
| International Standard Book Number | 9788131741795 |
| Qualifying information | (electronic bk.) |
| 035 ## - SYSTEM CONTROL NUMBER | |
| System control number | (MiAaPQ)EBC5125983 |
| 035 ## - SYSTEM CONTROL NUMBER | |
| System control number | (Au-PeEL)EBL5125983 |
| 035 ## - SYSTEM CONTROL NUMBER | |
| System control number | (CaONFJC)MIL265217 |
| 035 ## - SYSTEM CONTROL NUMBER | |
| System control number | (OCoLC)1024286845 |
| 040 ## - CATALOGING SOURCE | |
| Original cataloging agency | MiAaPQ |
| Language of cataloging | eng |
| Description conventions | rda |
| -- | pn |
| Transcribing agency | MiAaPQ |
| Modifying agency | MiAaPQ |
| 082 ## - DEWEY DECIMAL CLASSIFICATION NUMBER | |
| Edition number | 23rd |
| Classification number | 005.1 |
| 100 1# - MAIN ENTRY--PERSONAL NAME | |
| Personal name | Dustin, Elfriede. |
| 245 10 - TITLE STATEMENT | |
| Title | Effective Software Testing. |
| 300 ## - PHYSICAL DESCRIPTION | |
| Extent | 1 online resource (292 pages) |
| 505 0# - FORMATTED CONTENTS NOTE | |
| Formatted contents note | Cover -- Contents -- Preface -- Acknowledgments -- 1. Requirements Phase -- Item 1: Involve Testers from the Beginning -- Item 2: Verify the Requirements -- Item 3: Design Test Procedures As Soon As Requirements Are Available -- Item 4: Ensure That Requirement Changes Are Communicated -- Item 5: Beware of Developing and Testing Based on an Existing System -- 2. Test Planning -- Item 6: Understand the Task At Hand and the Related Testing Goal -- Item 7: Consider the Risks -- Item 8: Base Testing Efforts on a Prioritized Feature Schedule -- Item 9: Keep Software Issues in Mind -- Item 10: Acquire Effective Test Data -- Item 11: Plan the Test Environment -- Item 12: Estimate Test Preparation and Execution Time -- 3. The Testing Team -- Item 13: Define Roles and Responsibilities -- Item 14: Require a Mixture of Testing Skills, Subject-Matter Expertise, and Experience -- Item 15: Evaluate the Tester's Effectiveness -- 4. The System Architecture -- Item 16: Understand the Architecture and Underlying Components -- Item 17: Verify That the System Supports Testability -- Item 18: Use Logging to Increase System Testability -- Item 19: Verify That the System Supports Debug and Release Execution Modes -- 5. Test Design and Documentation -- Item 20: Divide and Conquer -- Item 21: Mandate the Use of a Test-Procedure Template and Other Test-Design Standards -- Item 22: Derive Effective Test Cases from Requirements -- Item 23: Treat Test Procedures As "Living" Documents -- Item 24: Utilize System Design and Prototypes -- Item 25: Use Proven Testing Techniques when Designing Test-Case Scenarios -- Item 26: Avoid Including Constraints and Detailed Data Elements within Test Procedures -- Item 27: Apply Exploratory Testing -- 6. Unit Testing -- Item 28: Structure the Development Approach to Support Effective Unit Testing. |
| 505 8# - FORMATTED CONTENTS NOTE | |
| Formatted contents note | Item 29: Develop Unit Tests in Parallel or Before the Implementation -- Item 30: Make Unit-Test Execution Part of the Build Process -- 7. Automated Testing Tools -- Item 31: Know the Different Types of Testing-Support Tools -- Item 32: Consider Building a Tool Instead of Buying One -- Item 33: Know the Impact of Automated Tools on the Testing Effort -- Item 34: Focus on the Needs of Your Organization -- Item 35: Test the Tools on an Application Prototype -- 8. Automated Testing: Selected Best Practices -- Item 36: Do Not Rely Solely on Capture/Playback -- Item 37: Develop a Test Harness When Necessary -- Item 38: Use Proven Test-Script Development Techniques -- Item 39: Automate Regression Tests When Feasible -- Item 40: Implement Automated Builds and Smoke Tests -- 9. Nonfunctional Testing -- Item 41: Do Not Make Nonfunctional Testing an Afterthought -- Item 42: Conduct Performance Testing with Production-Sized Databases -- Item 43: Tailor Usability Tests to the Intended Audience -- Item 44: Consider All Aspects of Security, for Specific Requirements and System-Wide -- Item 45: Investigate the System's Implementation To Plan for Concurrency Tests -- Item 46: Set Up an Efficient Environment for Compatibility Testing -- 10. Managing Test Execution -- Item 47: Clearly Define the Beginning and End of the Test-Execution Cycle -- Item 48: Isolate the Test Environment from the Development Environment -- Item 49: Implement a Defect-Tracking Life Cycle -- Item 50: Track the Execution of the Testing Program -- Index -- A -- B -- C -- D -- E -- F -- G -- G -- I -- K -- L -- M -- N -- O -- P -- Q -- R -- S -- T -- U -- V -- W. |
| 590 ## - LOCAL NOTE (RLIN) | |
| Local note | Electronic reproduction. Ann Arbor, Michigan : ProQuest Ebook Central, 2018. Available via World Wide Web. Access may be limited to ProQuest Ebook Central affiliated libraries. |
| 655 #4 - INDEX TERM--GENRE/FORM | |
| Genre/form data or focus term | Electronic books. |
| 776 08 - ADDITIONAL PHYSICAL FORM ENTRY | |
| Display text | Print version: |
| Main entry heading | Dustin, Elfriede |
| Title | Effective Software Testing: 50 Specific Ways To Improve Your Testing |
| Place, publisher, and date of publication | Noida : Pearson India,c2002 |
| 797 2# - LOCAL ADDED ENTRY--CORPORATE NAME (RLIN) | |
| Corporate name or jurisdiction name as entry element | ProQuest (Firm) |
| 856 40 - ELECTRONIC LOCATION AND ACCESS | |
| Uniform Resource Identifier | <a href="https://ebookcentral.proquest.com/lib/cethalassery/detail.action?docID=5125983">https://ebookcentral.proquest.com/lib/cethalassery/detail.action?docID=5125983</a> |
| Public note | Click to View |
| 942 ## - ADDED ENTRY ELEMENTS (KOHA) | |
| Source of classification or shelving scheme | Dewey Decimal Classification |
| Koha item type | Books |
| Withdrawn status | Lost status | Source of classification or shelving scheme | Materials specified (bound volume or other part) | Damaged status | Not for loan | Home library | Current library | Shelving location | Date acquired | Total Checkouts | Full call number | Barcode | Date last seen | Price effective from | Koha item type |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Dewey Decimal Classification | Online access | CENTRAL LIBRARY | Digital Library | Digital Library | 04/01/2019 | 005.1 DUS-E | E0097 | 04/01/2019 | 04/01/2019 | E- Books |