1. About the Book

About "The Art of Creative Destruction"

The Art of Creative Destruction comprehensively covers all aspects of software testing, without being verbose. It deals with the practical aspects of testing, and covers certain special topics that are unique and hard to find elsewhere. It is full of diagrammatic illustrations, and is written in a clear and concise style.

It has special coverage on Agile Testing Methodology - so vital to deliver quality product. It comprehensively brings forth all aspects of Agile Testing, along with illustrative examples.

It is meant both for the techies and for the non-techies. Developers, designers, project leads, project managers would find it useful, besides testers and developers of test automation. End-users conducting UAT (User Acceptance Testing) and Top Management, planning/reviewing software testing, would also find it useful.

Book Particulars:

Paperback:  248 pages

Publisher:  Shroff Publishers and Distributors Pvt. Ltd. (shroffpublishers.com)

Language:  English

ISBN-13:  978-8184048827

Product Dimensions:  8.9 x 6.9 x 0.7 inches

Shipping Weight:  1.2 pounds


Preface to “The Art of Creative Destruction”

by Rajnikant Puranik

My objectives behind writing this book are :

Cover areas that are not covered in any other book on testing,

at least not in the books that I have read. While heading development of Core Banking and Treasury Products, I very much wished to also develop automated regression suite in parallel, and desperately searched the Web and the available books for relevant inputs to accomplish the same. Reading them proved useful, but I found little practical guidelines to achieve the objective. I then decided that sometime in future when I have time to write a book, I would certainly cover this uncovered area, based on my own practical experience. I am sure you would find lots of matter in this book – also illustrated through diagrams – that, to my knowledge, is not covered elsewhere.

Illustrated.

A picture is worth a thousand words. One of the objectives, therefore, has been to illustrate the concepts through diagrams as much as possible.

Non-verbose.

Where is the time to read a tome. Essentials often get buried in the thickness; and therefore, this book, initially over 500 pages, has been mercilessly condensed to a little over 200 pages, with the objective of making it readable, nondaunting, non-verbose, yet comprehensive.

Comprehensive.

Care has been taken to cover all relevant topics, in a clear and concise manner.

Meant for :

Testing is an area not just for testers. It is a critical area about which besides developers, project managers, domain experts, test-engineers and end-users involved in UAT; the senior and the top management also needs to be well

aware – for it is critical to cost and quality, and hence, to business. This book is meant as much for testers, as for developers, project managers, end-users involved in UAT, domain experts, and the senior and top management.

Focus : Test Automation.

The book focuses on test automation and illustrates how to accomplish the same. It takes you beyond the commonly held notion that test-automation is but usage of Recording & Playback test-automation tools like Rational Robot or WinRunner, and shows that it is indeed much, much more than that.

Business Domain used for Illustration : Banking.

Bankers involved in the IT area, CTOs, those in Banking Units of Software Development, and Software Maintenance and Testing Cos. would find it particularly useful as many of the illustrations are from the banking domain. However, the illustrations serve a general purpose as well, and would be found useful by others too.

It also illustrates how a totally hand-off, automated testing is feasible.

Agile Testing.

Traditional testing is a dinosaur. Agile Methodolgy and Agile Testing are practically proving to be a much more likely to ensure success of projects and for creation of quality working software, better adapted to client’s requirements, at relatively lesser costs, with lower risks, lesser efforts, and in a shorter time frame. I have therefore devoted a section to Agile Testing.

I have also advocated manadatory test automation suite under “Ensuring Quality: A Case for Manadatory Test Suite with each Software Product”. One way to ensure this would be Agile Testing, with its stress on test automation.

I do hope you find the book useful.