Rev. ed. of: Studying a study and testing a test / Richard K. Riegelman.

This complete package of textbook, interactive exercises, and real research articles is designed for use alongside Journal Clubs conducted in medical, nursing, and other health professions programs, as well as in evidence-based medicine courses. It employs the authors’ proven, step-by-step framework, and strengthens students’ and residents’ ability to recognize a meaningful study, identify potential study flaws, and apply solid evidence in clinical decision making. Class tested by students in leading medical schools, Studying a Study and Testing a Test, Seventh Edition, features a suite of resources ideal for traditional learning, flipped-classroom approaches, and distance learning:

How do successful agile teams deliver bug-free, maintainable software—iteration after iteration? The answer is: By seamlessly combining development and testing. On such teams, the developers write testable code that enables them to verify it using various types of automated tests. This approach keeps regressions at bay and prevents “testing crunches”—which otherwise may occur near the end of an iteration—from ever happening. Writing testable code, however, is often difficult, because it requires knowledge and skills that cut across multiple disciplines. In Developer Testing, leading test expert and mentor Alexander Tarlinder presents concise, focused guidance for making new and legacy code far more testable. Tarlinder helps you answer questions like: When have I tested this enough? How many tests do I need to write? What should my tests verify? You’ll learn how to design for testability and utilize techniques like refactoring, dependency breaking, unit testing, data-driven testing, and test-driven development to achieve the highest possible confidence in your software. Through practical examples in Java, C#, Groovy, and Ruby, you’ll discover what works—and what doesn’t. You can quickly begin using Tarlinder’s technology-agnostic insights with most languages and toolsets while not getting buried in specialist details. The author helps you adapt your current programming style for testability, make a testing mindset “second nature,” improve your code, and enrich your day-to-day experience as a software professional. With this guide, you will Understand the discipline and vocabulary of testing from the developer’s standpoint Base developer tests on well-established testing techniques and best practices Recognize code constructs that impact testability Effectively name, organize, and execute unit tests Master the essentials of classic and “mockist-style” TDD Leverage test doubles with or without mocking frameworks Capture the benefits of programming by contract, even without runtime support for contracts Take control of dependencies between classes, components, layers, and tiers Handle combinatorial explosions of test cases, or scenarios requiring many similar tests Manage code duplication when it can’t be eliminated Actively maintain and improve your test suites Perform more advanced tests at the integration, system, and end-to-end levels Develop an understanding for how the organizational context influences quality assurance Establish well-balanced and effective testing strategies suitable for agile teams

"[The anti-testing] movement now has a guidebook. . . . Kamenetz shows how fundamentally American it would be to move toward a more holistic system." -- New York Times Book Review The Test is an essential and critically acclaimed book for any parent confounded by our national obsession with standardized testing. It recounts the shocking history and tempestuous politics of testing and borrows strategies from fields as diverse as games, neuroscience, and ancient philosophy to help children cope. It presents the stories of families, teachers, and schools maneuvering within and beyond the existing educational system, playing and winning the testing game. And it points the way toward a hopeful future of better tests and happier kids.

How to Find and Fix the Killer Software Bugs that Evade Conventional Testing In Exploratory Software Testing, renowned software testing expert James Whittaker reveals the real causes of today’s most serious, well-hidden software bugs--and introduces powerful new “exploratory” techniques for finding and correcting them. Drawing on nearly two decades of experience working at the cutting edge of testing with Google, Microsoft, and other top software organizations, Whittaker introduces innovative new processes for manual testing that are repeatable, prescriptive, teachable, and extremely effective. Whittaker defines both in-the-small techniques for individual testers and in-the-large techniques to supercharge test teams. He also introduces a hybrid strategy for injecting exploratory concepts into traditional scripted testing. You’ll learn when to use each, and how to use them all successfully. Concise, entertaining, and actionable, this book introduces robust techniques that have been used extensively by real testers on shipping software, illuminating their actual experiences with these techniques, and the results they’ve achieved. Writing for testers, QA specialists, developers, program managers, and architects alike, Whittaker answers crucial questions such as: • Why do some bugs remain invisible to automated testing--and how can I uncover them? • What techniques will help me consistently discover and eliminate “show stopper” bugs? • How do I make manual testing more effective--and less boring and unpleasant? • What’s the most effective high-level test strategy for each project? • Which inputs should I test when I can’t test them all? • Which test cases will provide the best feature coverage? • How can I get better results by combining exploratory testing with traditional script or scenario-based testing? • How do I reflect feedback from the development process, such as code changes?

Software Engineering / Testing Test Process Improvement A practical step-by-step guide to structured testing Tim Koomen Martin Pol ¿If competitiveness is an issue in your market, IT will be vital, and this book will help you to deal with the problems it will bring along.¿ Henk W Broeders, Executive Board, CAP Gemini ¿I was introduced to TPI and suddenly the penny dropped...This was quite a revelation... I recommend that you try the ideas suggested in this book... use the TPI method to improve your test process.¿ Stephen K Allott, Senior Consultant, ImagoQA Ltd ¿The application of TPI enables us to raise our global testing organization to the next professional level. I am absolutely convinced that everybody using TPI in a similar way will experience the same added value.¿ Dr Hans Voorthuyzen, Global Manager Product Testing Group, Baan Software testing is an essential part of software development but many organizations regard it as an uncontrollable part of the process and find it difficult to take steps to improve it. In Test Process Improvement, Tim Koomen and Martin Pol give practical suggestions for improving the testing process in a gradual and controlled manner, with realistic goals in terms of quality, lead time and costs. The book describes and explains the Test Process Improvement (TPI) model, tried and tested by numerous professional testers, which provides a structured framework to be used either for improving an existing test process or for developing a new process from scratch. The authors use their in-depth knowledge and extensive experience to provide practical guidance and a framework that enables the reader to adapt the model for use in his/her organization. If you are involved in testing software systems and are aiming to implement a successful and structured process, you will find this book an invaluable resource. About the authors Tim Koomen is a professional tester for IQUIP Informatica B.V. in the Netherlands, where he is a member of the R&D team covering issues such as automated testing and testfactories. He is currently advising organizations on how to improve their testing processes using the TPI model. He regularly presents at conferences and training sessions throughout Europe. Martin Pol has over 25 years of experience in structured testing, currently working as an R&D manager with responsibility for development and innovation of testing methods for IQUIP Informatica B.V. and GiTek Software N.V. in Belgium. He was involved in the development of the structured testing approach, TMap, and the creation of TPI. He is a highly regarded speaker at conferences and training courses throughout Europe and the USA, having twice chaired EuroSTAR. He recently received the European Testing Excellence Award for his contribution to the field of testing. [barcode box] Visit us on the World Wide Web at: http: //www.awl-he.com/computing http: //www.awl.com/cseng Back of Jacket

2012 Jolt Award finalist! Pioneering the Future of Software Test Do you need to get it right, too? Then, learn from Google. Legendary testing expert James Whittaker, until recently a Google testing leader, and two top Google experts reveal exactly how Google tests software, offering brand-new best practices you can use even if you’re not quite Google’s size...yet! Breakthrough Techniques You Can Actually Use Discover 100% practical, amazingly scalable techniques for analyzing risk and planning tests...thinking like real users...implementing exploratory, black box, white box, and acceptance testing...getting usable feedback...tracking issues...choosing and creating tools...testing “Docs & Mocks,” interfaces, classes, modules, libraries, binaries, services, and infrastructure...reviewing code and refactoring...using test hooks, presubmit scripts, queues, continuous builds, and more. With these techniques, you can transform testing from a bottleneck into an accelerator–and make your whole organization more productive!