Hello there, I have an online exam tomorrow at 10 AM pacific time.- Class Name: Software Quality Assurance.- The exam is 44 multiple-choice questions.- The exam is 2 hours long.- In order to pass the exam you need to get at least 32 questions correct out of the 44 questions.- I'm gonna send you the exam questions as pictures through "Hangouts"- M Hangouts email is:
[email protected] Here is a sample of the questions:https://quizlet.com/305626987/c857-software-quality-assurance-pre-assessment-flash-cards/
Thank you,
Software Quality Assurance Software Quality Assurance Syllabus The Book (The Art Of Software Testing): https://fktpm.ru/file/114-the-art-of-software-testing-3-edition.pdf Chapter breakdown: ● Art of Software Testing Chapter 1: You can skim this. It's just an introduction of everything, I didn't get tested on it at all. So, I wouldn't recommend hard studying. ● Art of Software Testing Chapter 2: Take notes on WHAT testing actually is and what the purpose is. Also, take notes on what blackbox testing is and whitebox is. Know the difference between the two. This is a basic difference, and there will be more on chapter 4 about it, but just get the basic definitions they give. Also, I had one question regarding the "principles of testing", so while you do not need to memorize it all, just be familiar with it. ● Art of Software Testing Chapter 3: This chapter touches on the types of reviews. Learn what the walkthroughs, code inspections, peer reviews/ratings, and desk-checks are. Also, pay attention to the benefits they have (although, desk-checking doesn't really have one). ● Art of Software Testing Chapter 4: Test cases chapter goes more into whitebox vs blackbox. However, instead of getting the definitions of those, this time you should be focusing on the methodologies (equivalence partitioning, error guessing, decision coverage, etc.) and what they do. You don't have to go deep into what they do (like all the examples they have, etc.). Just make sure to have a basic understanding of what they are and how to tell them apart. ● Art of Software Testing Chapter 5: This chapter does not have many things to really focus on. Just focus on the definition of incremental, non-incremental, top-down, and bottom-up testing are. Again, just a basic definition so you can tell them apart. ● Art of Software Testing Chapter 6 (IMPORTANT CHAPTER): This is an important chapter to focus on. Mainly figure 6.3. You'll want to know what each development stage is and their corresponding test process. For example, you'll want to know what a requirement is and which testing it uses (which is acceptance testing). ALSO, take note of the 15 categories of test cases. Memorize the definitions used in figure 6.1, my OA had some questions about these. Also, take note of what regression testing, tracking procedures, and debugging procedures are used for. A big portion of the test is focused on all of these things in chapter 6. ● Art of Software Testing Chapter 7: Nothing too eventful here. You can really skim it. Just have a basic idea of what usability testing is and what it is used for. I wouldn't really focus on the process, etc. unless you're really interested in the topic. ● Art of Software Testing Chapter 8 (IMPORTANT CHAPTER): For this chapter, focus on the definitions of debugging by brute force, induction, deduction, backtracking, and testing. Know when to use these debugging methods as well. Also, read through the "Error-Locating Principles", "Error-Repairing Techniques", and "Error Analysis". This will help you with some of the scenario-based questions on the test. https://fktpm.ru/file/114-the-art-of-software-testing-3-edition.pdf ● Art of Software Testing Chapter 9: I actually didn't have too many questions on the Agile method. However, I would just know what the agile method is and how it works. I didn't have anything on Extreme Programming, but it might be good to skim through just in case. ● Practical Insight into CMMI Chapter 13: Focus on which reviews are considered formal and which are considered informal. Also, knowing what a buddy-check, circulation, and technical interview are will be helpful for the test. Other than that, not too much to focus on here as the majority of what you need was discussed in chapter 3. THE ART OF SOFTWARE TESTING FFIRS 08/25/2011 11:31:15 Page 2 FFIRS 08/25/2011 11:31:15 Page 1 THE ART OF SOFTWARE TESTING FFIRS 08/25/2011 11:31:15 Page 2 FFIRS 08/25/2011 11:31:15 Page 3 THE ART OF SOFTWARE TESTING Third Edition GLENFORD J. MYERS TOM BADGETT COREY SANDLER John Wiley & Sons, Inc. FFIRS 08/25/2011 11:31:15 Page 4 Copyright# 2012 by Word Association, Inc. All rights reserved. Published by John Wiley & Sons, Inc., Hoboken, New Jersey. Published simultaneously in Canada. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning, or otherwise, except as permitted under Section 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, Inc., 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600, or on the web at www.copyright.com. Requests to the Publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 111 River Street, Hoboken, NJ 07030, (201) 748-6011, fax (201) 748-6008, or online at www.wiley.com/go/permissions. Limit of Liability/Disclaimer of Warranty: While the publisher and author have used their best efforts in preparing this book, they make no representations or warranties with respect to the accuracy or completeness of the contents of this book and specifically disclaim any implied warranties of merchantability or fitness for a particular purpose. No warranty may be created or extended by sales representatives or written sales materials. The advice and strategies contained herein may not be suitable for your situation. You should consult with a professional where appropriate. Neither the publisher nor author shall be liable for any loss of profit or any other commercial damages, including but not limited to special, incidental, consequential, or other damages. For general information on our other products and services or for technical support, please contact our Customer Care Department within the United States at (800) 762-2974, outside the United States at (317) 572-3993 or fax (317) 572-4002. Wiley also publishes its books in a variety of electronic formats. Some content that appears in print may not be available in electronic books. For more information about Wiley products, visit our website at www.wiley.com. Library of Congress Cataloging-in-Publication Data: Myers, Glenford J., 1946- The art of software testing / Glenford J. Myers, Corey Sandler, Tom Badgett. — 3rd ed. p. cm. Includes index. ISBN 978-1-118-03196-4 (cloth); ISBN 978-1-118-13313-2 (ebk); ISBN 978-1-118-13314-9 (ebk); ISBN 978-1-118-13315-6 (ebk) 1. Computer software—Testing. 2. Debugging in computer science. I. Sandler, Corey, 1950- II. Badgett, Tom. III. Title. QA76.76.T48M894 2011 005.1 04—dc23 2011017548 Printed in the United States of America 10 9 8 7 6 5 4 3 2 1 http://www.wiley.com/go/permissions http://www.wiley.com http://www.copyright.com FTOC 08/25/2011 11:33:28 Page 5 Contents Preface vii Introduction ix 1 A Self-Assessment Test 1 2 The Psychology and Economics of Software Testing 5 3 Program Inspections, Walkthroughs, and Reviews 19 4 Test-Case Design 41 5 Module (Unit) Testing 85 6 Higher-Order Testing 113 7 Usability (User) Testing 143 8 Debugging 157 9 Testing in the Agile Environment 175 10 Testing Internet Applications 193 11 Mobile Application Testing 213 Appendix Sample Extreme Testing Application 227 Index 233 v FTOC 08/25/2011 11:33:28 Page 6 FPREF 08/08/2011 17:19:4 Page 7 Preface In 1979, Glenford Myers published a book that turned out to be a classic.The Art of Software Testing has stood the test of time—25 years on the publisher’s list of available books. This fact alone is a testament to the solid, essential, and valuable nature of his work. During that same time, the authors of this edition (the third) of The Art of Software Testing published, collectively, more than 200 books, most of them on computer software topics. Some of these titles sold very well and, like this one, have gone through multiple versions. Corey Sandler’s Fix Your Own PC, for example, is in its eighth edition as this book goes to press; and Tom Badgett’s books on Microsoft PowerPoint and other Office titles have gone through four or more editions. However, unlike Myers’s book, none of these remained current for more than a few years. What is the difference? The newer books covered more transient topics—operating systems, applications software, security, communica- tions technology, and hardware configurations. Rapid changes in computer hardware and software technology during the 1980s and 1990s necessi- tated frequent changes and updates to these topics. Also during that period hundreds of books about software testing were published. They, too, took a more transient approach to the topic. The Art of Software Testing alone gave the industry a long-lasting, foundational guide to one of the most important computer topics: How do you ensure that all of the software you produce does what it was designed to do, and— just as important—doesn’t do what it isn’t supposed to do? The edition you are reading today retains the foundational philosophy laid by Myers more than three decades ago. But we have updated the examples to include more current programming languages, and we have addressed topics that were not yet topics when Myers wrote the first edition: Web programming, e-commerce, Extreme (Agile) programming and testing, and testing applications for mobile devices. vii FPREF 08/08/2011 17:19:4 Page 8 Along the way, we never lost sight of the fact that a new classic must stay true to its roots, so our version also offers you a software testing philoso- phy, and a process that works across current and unforeseeable future hardware and software platforms. We hope that the third edition of The Art of Software Testing, too, will span a generation of software designers and developers. viii Preface CINTRO 08/08/2011 17:23:34 Page 9 Introduction A t the time this book was first published, in 1979, it was a well-knownrule of thumb that in a typical programming project approximately 50 percent of the elapsed time and more than 50 percent of the total cost were expended in testing the program or system being developed. Today, a third of a century and two book updates later, the same holds true. There are new development systems, languages with built-in tools, and programmers who are used to developing more on the fly. But testing continues to play an important part in any software development project. Given these facts, you might expect that by this time program testing would have been refined into an exact science. This is far from the case. In fact, less seems to be known about software testing than about any other aspect of software development. Furthermore, testing has been an out-of- vogue subject; it was so when this book was first published and, un- fortunately, this has not changed. Today there are more