Software testing

Software testing is conducted to provide stakeholders with information about the quality of a product under testing. The book, which is a result of the two decades of teaching experience of the author, aims to present testing concepts and methods that can be used in practice. The text will help readers to learn how to find faults in software before it is made available to users. A judicious mix of software testing concepts, solved problems and real-life case studies makes the book ideal for a basic course in software testing. The book will be a useful resource for senior undergraduate/graduate students of engineering, academics, software practitioners and researchers.

Title from publisher's bibliographic system (viewed on 05 Oct 2015).

Cover; Title; Copyright; Contents; List of Figures; List of Tables; Preface; Acknowledgements; 1 Introduction; 1.1 SOME SOFTWARE FAILURES; 1.1.1 The Explosion of the Ariane 5 Rocket; 1.1.2 The Y2K Problem; 1.1.3 The USA Star-Wars Program; 1.1.4 Failure of London Ambulance System; 1.1.5 USS Yorktown Incident; 1.1.6 Accounting Software Failures; 1.1.7 Experience of Windows XP; 1.2 TESTING PROCESS; 1.2.1 What is Software Testing?; Modifications in the program 'Minimum'; 1.2.2 Why Should We Test?; 1.2.3 Who Should We Do the Testing?; 1.2.4 What Should We Test?; 1.3 SOME TERMINOLOGIES

1.3.1 Program and Software1.3.2 Verification and Validation; 1.3.3 Fault, Error, Bug and Failure; 1.3.4 Test, Test Case and Test Suite; 1.3.5 Deliverables and Milestones; 1.3.6 Alpha, Beta and Acceptance Testing; 1.3.7 Quality and Reliability; 1.3.8 Testing, Quality Assurance and Quality Control; 1.3.9 Static and Dynamic Testing; 1.3.10 Testing and Debugging; 1.4 LIMITATIONS OF TESTING; 1.4.1 Errors in the Software Requirement and Specification Document; 1.4.2 Logical Bugs; 1.4.3 Difficult to Measure the Progress of Testing; 1.5 THE V SHAPED SOFTWARE LIFE CYCLE MODEL

1.5.1 Graphical Representation1.5.2 …