Interview Questions and Answers for QTP (Quick Test Professional)

Friday, July 01, 2005

Software Testing books -

The best thing about "Testing Computer Software" is its practical point-by-point guide to everyday software testing, from creating a test plan, to writing effective bug reports, to working with programming staff and management to fix bugs.

Topics covered: test case design, test planning, project lifecycle overview, software errors, boundary conditions, bug reports, regression testing, black box testing, software quality and reliability, managing test teams, printer testing, internationalization, and managing legal risk.


While this book does cover some rules of thumb for testing techniques, it goes further. It provides insight into the human element of testing and gives practical advice on how to communicate defects, trust in the doers to make estimates, understand the importance of a diverse culture and other areas that have a significant impact on the development process. This is all done well within the context of the impact to software testing.


For a practical guide to software testing, readers can look to Rex Black's "Managing the Testing Process", a compendium of real-world advice on managing software testing successfully.
Early sections examine the design of test plans, along with strategies for assessing and prioritizing risk as well as catching bugs through effective testing. Sample case studies include a network hardware device and a Java word processor.

Throughout this book, a variety of documents (including Excel spreadsheets and Access databases) are presented to get you started on your own testing projects. (all sample documents are included on the accompanying CD-ROM.) The book also looks at metrics for measuring the performance of your testing operation.

"Managing the Testing Process" shows how a bug-tracking database is the most effective model for managing the testing cycle. This book is chock-full of advice on testing management. The author also presents dozens of tips for succeeding in the software Q/A job market.


"Software Testing and Continuous Quality Improvement" illustrates a quality framework for software testing in traditional structured and unstructured environments. Section I reviews modern QA principles and best practices. Section II examines the waterfall development methodology. The next section contrasts waterfall development methodology with the rapid application spiral environment. Section IV discusses fundamental challenges of maintaining and improving existing systems. Section V contains a history of software testing, previews future testing tools, and guides the choosing of proper tools for various environments. It provides examples of some of the most popular products, and offers a detailed methodology for evaluating them.


This book shows the latest technologies and expert tools, tips, and techniques for testing Web applications that run across many platforms and networks, including desktop and wired/wireless mobile clients. You'll quickly be able to maximize productivity, minimize quality risks, and optimize success in the Internet economy.
With numerous real-world examples at hand, you'll learn how to:
- Analyze the complex Web-application model and gain a better understanding of the effective practices for deploying a successful testing strategy
- Design smart test cases, utilize best test practices, and perform effective bug analysis
- Identify similarities and differences between testing desktop and mobile Web applications, and devise test plans for each platform
- Apply advanced and specialized testing techniques including security testing, performance testing, database testing, and server-side testing.


"How to Break Software" is a departure from conventional testing in which testers prepare a written test plan and then use it as a script when testing the software. The testing techniques in this book are as flexible as conventional testing is rigid. And flexibility is needed in software projects in which requirements can change, bugs can become features and schedule pressures often force plans to be reassessed. Software testing is not such an exact science that one can determine what to test in advance and then execute the plan and be done with it. Instead of a plan, intelligence, insight, experience and a "nose for where the bugs are hiding" should guide testers. This book helps testers develop this insight.

The techniques presented in this book not only allow testers to go off-script, they encourage them to do so. Don't blindly follow a document that may be out of date and that was written before the product was even testable. Instead, use your head! Open your eyes! Think a little, test a little and then think a little more. This book does teach planning, but in an "on- the-fly while you are testing" way. It also encourages automation with many repetitive and complex tasks that require good tools (one such tool is shipped with this book on the companion CD). However, tools are never used as a replacement for intelligence. Testers do the thinking and use tools to collect data and help them explore applications more efficiently and effectively.


If you're a software tester or in the software quality assurance field, especially if you're interested in security, you need to read this book as it will likely be an eye-opener. It's not full of shocking anecdotes to scare developers into writing better software, it's a handbook of what to look for when testing software after you think you've done all your testing, and at the same time gives developers and project managers good information on how to design, code, and state requirements better.

If you're a security person, especially the burgeoning field of application security, you might also find this book pretty enlightining. Everyone's heard of penetration testing and vulnerability assessment, but typically only in the context of attacking remotely over a network. This book shows you how to attack the software on your local machine.


In this book, you'll find the latest methodologies for the design of effective test cases, including information on psychological and economic principles, managerial aspects, test tools, high-order testing, code inspections, and debugging. Accessible, comprehensive, and always practical, this edition provides the key information you need to test successfully, whether a novice or a working programmer.


This book is a distillation of a broad array of concepts, from requirements analysis to automated testing tools to evaluating how effective a tester is. This wide scope gives the book a broad appeal and it serves to make it clear that there is quite a bit going on in the world of testing.
This is an excellent reference book for the average test group within an organization and is certainly worth having in your library if you in any way deal with the world of quality assurance or quality testing.


This text describes MITs (Most Important Tests), a risk based test methodology. The MITs are determined using various methods, including path analysis, boundary value analysis, expert interviews, and test ranking. MITs makes use of prioritized test cases, which collectively are referred to as a test inventory. The book is organized in 3 sections. Chapters 1 through 5 focus on background concepts. Chapters 6 through 8 focus on the test inventory and how to create it. Chapters 9 through 14 discuss risk analysis, test techniques , and test planning and estimation.
In addition to being aligned to product line development, this book's approach can also be easily tailored to rapid, iterative development approaches such as agile methods. If you are working in an internal development environment that uses 'heavier' development lifecycles this book is not going to fit; however, if you work in a product-oriented environment this book will not only change your thinking, but will provide the basis for an integrated development-marketing approach that could make a real difference in competitive advantage.


"Automated Software Testing" presents a methodology for test managers called Automated Testing Lifecycle Management (ATLM). This isncludes initial planning, budgeting, staffing, building a test plan and choosing test tools to executing tests and even improving your testing process the next time around. Though somewhat thickly written--with plenty of software engineering terminology--this book can also be useful to more practically minded readers because of its many sample test documents. (Besides numerous lists and charts outlining the steps in the ATLM process, the book presents a sample test plan, budget estimates, and staffing guides.)
A truly standout feature is the book's survey of currently available automated tools that can be used throughout the testing cycle, as well as how to choose the right ones for your next project.


This book provides the latest in standards for measuring how good your organization's commitment to software testing is and many ways to improve it. In all, with its numerous lists and practical step-by-step guide to testing, this book points the way toward more economical and effective software testing.

This book's major strength is its meticulous 11-step guide to all aspects of today's software testing process--from initial analysis and test planning to testing software installation and looking at ways to improve the testing cycle the next time around. The book is filled with to-do lists that enumerate the resources and tasks required for each step with helpful hints for what to do, how to work with management, and how to staff and execute a test plan from start to finish. (There is a chapter devoted to each of the 11 steps.)


QTP and Winrunner Questions and Answers
Contact: qualityvista @

Post to: IpadIt! | blinkbits | blinklist | Blogmarks | co.mments | | | digg It! | Fark| feedmelinks | Furl | LinkaGoGo | Ma.gnolia | Netscape | Newsvine | Netvouz | RawSugar | Reddit | scuttle | Shadows | Shoutwire | Simpy | Smarking | Spurl | TailRank | Wists | YahooMyWeb!


At 2:26 PM, February 06, 2006, Anonymous Anonymous said...

Well, our lists of 'must read' software testing books are almost the same!:) Mine also includes 'How to break software security' by James A. Whittaker and 'The Web Testing Companion: The Insider's Guide to Efficient and Effective Tests' by Lydia Ash.


Post a Comment

<< Home