Download or read book Agile Testing written by Lisa Crispin and published by Pearson Education. This book was released on 2009 with total page 576 pages. Available in PDF, EPUB and Kindle. Book excerpt: Crispin and Gregory define agile testing and illustrate the tester's role with examples from real agile teams. They teach you how to use the agile testing quadrants to identify what testing is needed, who should do it, and what tools might help. The book chronicles an agile software development iteration from the viewpoint of a tester and explains the seven key success factors of agile testing.

Download or read book The Agile Testing Collection written by Janet Gregory and published by Addison-Wesley Professional. This book was released on 2015-06-22 with total page 1409 pages. Available in PDF, EPUB and Kindle. Book excerpt: A Comprehensive Collection of Agile Testing Best Practices: Two Definitive Guides from Leading Pioneers Janet Gregory and Lisa Crispin haven’t just pioneered agile testing, they have also written two of the field’s most valuable guidebooks. Now, you can get both guides in one indispensable eBook collection: today’s must-have resource for all agile testers, teams, managers, and customers. Combining comprehensive best practices and wisdom contained in these two titles, The Agile Testing Collection will help you adapt agile testing to your environment, systematically improve your skills and processes, and strengthen engagement across your entire development team. The first title, Agile Testing: A Practical Guide for Testers and Agile Teams, defines the agile testing discipline and roles, and helps you choose, organize, and use the tools that will help you the most. Writing from the tester’s viewpoint, Gregory and Crispin chronicle an entire agile software development iteration, and identify and explain seven key success factors of agile testing. The second title, More Agile Testing: Learning Journeys for the Whole Team, addresses crucial emerging issues, shares evolved practices, and covers key issues that delivery teams want to learn more about. It offers powerful new insights into continuous improvement, scaling agile testing across teams and the enterprise, overcoming pitfalls of automation, testing in regulated environments, integrating DevOps practices, and testing mobile/embedded and business intelligence systems. The Agile Testing Collection will help you do all this and much more. Customize agile testing processes to your needs, and successfully transition to them Organize agile teams, clarify roles, hire new testers, and quickly bring them up to speed Engage testers in agile development, and help agile team members improve their testing skills Use tests and collaborate with business experts to plan features and guide development Design automated tests for superior reliability and easier maintenance Plan “just enough,” balancing small increments with larger feature sets and the entire system Test to identify and mitigate risks, and prevent future defects Perform exploratory testing using personas, tours, and test charters with session- and thread-based techniques Help testers, developers, and operations experts collaborate on shortening feedback cycles with continuous integration and delivery Both guides in this collection are thoroughly grounded in the authors’ extensive experience, and supported by examples from actual projects. Now, with both books integrated into a single, easily searchable, and cross-linked eBook, you can learn from their experience even more easily.

Download or read book More Agile Testing written by Janet Gregory and published by Pearson Education. This book was released on 2015 with total page 536 pages. Available in PDF, EPUB and Kindle. Book excerpt: Janet Gregory and Lisa Crispin pioneered the agile testing discipline with their previous work, Agile Testing. Now, in More Agile Testing, they reflect on all they've learned since. They address crucial emerging issues, share evolved agile practices, and cover key issues agile testers have asked to learn more about. Packed with new examples from real teams, this insightful guide offers detailed information about adapting agile testing for your environment; learning from experience and continually improving your test processes; scaling agile testing across teams; and overcoming the pitfalls of automated testing. You'll find brand-new coverage of agile testing for the enterprise, distributed teams, mobile/embedded systems, regulated environments, data warehouse/BI systems, and DevOps practices. You'll come away understanding - How to clarify testing activities within the team - Ways to collaborate with business experts to identify valuable features and deliver the right capabilities - How to design automated tests for superior reliability and easier maintenance - How agile team members can improve and expand their testing skills - How to plan "just enough," balancing small increments with larger feature sets and the entire system - How to use testing to identify and mitigate risks associated with your current agile processes and to prevent defects - How to address challenges within your product or organizational context - How to perform exploratory testing using "personas" and "tours" - Exploratory testing approaches that engage the whole team, using test charters with session- and thread-based techniques - How to bring new agile testers up to speed quickly-without overwhelming them The eBook edition of More Agile Testing also is available as part of a two-eBook collection, The Agile Testing Collection (9780134190624).

Download or read book Testing Extreme Programming written by Lisa Crispin and published by Addison-Wesley Professional. This book was released on 2003 with total page 332 pages. Available in PDF, EPUB and Kindle. Book excerpt: Testing is a cornerstone of XP, as tests are written for every piece of code before it is programmed. This workbook helps testers learn XP, and XP devotees learn testing. This new book defines how an XP tester can optimally contribute to a project, including what testers should do, when they should do it, and how they should do it.

Download or read book Agile Testing written by John Watkins and published by Cambridge University Press. This book was released on 2009-07-27 with total page 337 pages. Available in PDF, EPUB and Kindle. Book excerpt: In an IT world in which there are differently sized projects, with different applications, differently skilled practitioners, and on-site, off-site, and off-shored development teams, it is impossible for there to be a one-size-fits-all agile development and testing approach. This book provides practical guidance for professionals, practitioners, and researchers faced with creating and rolling out their own agile testing processes. In addition to descriptions of the prominent agile methods, the book provides twenty real-world case studies of practitioners using agile methods and draws upon their experiences to propose your own agile method; whether yours is a small, medium, large, off-site, or even off-shore project, this book provides personalized guidance on the agile best practices from which to choose to create your own effective and efficient agile method.

Download or read book Agile Testing written by Manfred Baumgartner and published by Springer Nature. This book was released on 2021-09-09 with total page 257 pages. Available in PDF, EPUB and Kindle. Book excerpt: This book is written by testers for testers. In ten chapters, the authors provide answers to key questions in agile projects. They deal with cultural change processes for agile testing, with questions regarding the approach and organization of software testing, with the use of methods, techniques and tools, especially test automation, and with the redefined role of the tester in agile projects. The first chapter describes the cultural change brought about by agile development. In the second chapter, which addresses agile process models such as Scrum and Kanban, the authors focus on the role of quality assurance in agile development projects. The third chapter deals with the agile test organization and the positioning of testing in an agile team. Chapter 4 discusses the question of whether an agile tester should be a generalist or a specialist. In Chapter 5, the authors turn to the methods and techniques of agile testing, emphasizing the differences from traditional, phase-oriented testing. In Chapter 6, they describe which documents testers still need to create in an agile project. Next, Chapter 7 explains the efficient use of test automation, which is particularly important in agile development, as it is the main instrument for project acceleration and is necessary to support state-of-the-art DevOps approaches and Continuous Integration. Chapter 8 then adds examples from test tool practice extending test automation to include test management functionality. Chapter 9 is dedicated to training and its importance, emphasizing the role of employee training in getting started with agile development. Finally, Chapter 10 summarizes the results of the agile journey in general with a special focus on testing. To make the aspects described even more tangible, the specific topics of this book are accompanied by the description of experiences from concrete software development projects of various organizations. The examples demonstrate that different approaches can lead to solutions that meet the specific challenges of agile projects.

Download or read book Lessons Learned in Software Testing written by Cem Kaner and published by John Wiley & Sons. This book was released on 2011-08-02 with total page 326 pages. Available in PDF, EPUB and Kindle. Book excerpt: Softwaretests stellen eine kritische Phase in der Softwareentwicklung dar. Jetzt zeigt sich, ob das Programm die entsprechenden Anforderungen erfüllt und sich auch keine Programmierungsfehler eingeschlichen haben. Doch wie bei allen Phasen im Software-Entwicklungsprozess gibt es auch hier eine Reihe möglicher Fallstricke, die die Entdeckung von Programmfehlern vereiteln können. Deshalb brauchen Softwaretester ein Handbuch, das alle Tipps, Tricks und die häufigsten Fehlerquellen genau auflistet und erläutert, damit mögliche Testfehler von vornherein vermieden werden können. Ein solches Handbuch ersetzt gut und gerne jahr(zehnt)elange Erfahrung und erspart dem Tester frustrierende und langwierige Trial-und-Error-Prozeduren. Chem Kaner und James Bach sind zwei der international führenden Experten auf dem Gebiet des Software Testing. Sie schöpfen hier aus ihrer insgesamt 30-jährigen Erfahrung. Die einzelnen Lektionen sind nach Themenbereichen gegliedert, wie z.B. Testdesign, Test Management, Teststrategien und Fehleranalyse. Jede Lektion enthält eine Behauptung und eine Erklärung sowie ein Beispiel des entsprechenden Testproblems. "Lessons Learned in Software Testing" ist ein unverzichtbarer Begleiter für jeden Software Tester.

Download or read book Essential Scrum written by Kenneth S. Rubin and published by Addison-Wesley Professional. This book was released on 2012 with total page 501 pages. Available in PDF, EPUB and Kindle. Book excerpt: This is a comprehensive guide to Scrum for all (team members, managers, and executives). If you want to use Scrum to develop innovative products and services that delight your customers, this is the complete, single-source reference you've been searching for. This book provides a common understanding of Scrum, a shared vocabulary that can be used in applying it, and practical knowledge for deriving maximum value from it.

Download or read book Coaching Agile Teams written by Lyssa Adkins and published by Addison-Wesley Professional. This book was released on 2010-05-18 with total page 523 pages. Available in PDF, EPUB and Kindle. Book excerpt: The Provocative and Practical Guide to Coaching Agile Teams As an agile coach, you can help project teams become outstanding at agile, creating products that make them proud and helping organizations reap the powerful benefits of teams that deliver both innovation and excellence. More and more frequently, ScrumMasters and project managers are being asked to coach agile teams. But it’s a challenging role. It requires new skills—as well as a subtle understanding of when to step in and when to step back. Migrating from “command and control” to agile coaching requires a whole new mind-set. In Coaching Agile Teams, Lyssa Adkins gives agile coaches the insights they need to adopt this new mind-set and to guide teams to extraordinary performance in a re-energized work environment. You’ll gain a deep view into the role of the agile coach, discover what works and what doesn’t, and learn how to adapt powerful skills from many allied disciplines, including the fields of professional coaching and mentoring. Coverage includes Understanding what it takes to be a great agile coach Mastering all of the agile coach’s roles: teacher, mentor, problem solver, conflict navigator, and performance coach Creating an environment where self-organized, high-performance teams can emerge Coaching teams past cooperation and into full collaboration Evolving your leadership style as your team grows and changes Staying actively engaged without dominating your team and stunting its growth Recognizing failure, recovery, and success modes in your coaching Getting the most out of your own personal agile coaching journey Whether you’re an agile coach, leader, trainer, mentor, facilitator, ScrumMaster, project manager, product owner, or team member, this book will help you become skilled at helping others become truly great. What could possibly be more rewarding?

Download or read book User Stories Applied written by Mike Cohn and published by Addison-Wesley Professional. This book was released on 2004-03-01 with total page 291 pages. Available in PDF, EPUB and Kindle. Book excerpt: Thoroughly reviewed and eagerly anticipated by the agile community, User Stories Applied offers a requirements process that saves time, eliminates rework, and leads directly to better software. The best way to build software that meets users' needs is to begin with "user stories": simple, clear, brief descriptions of functionality that will be valuable to real users. In User Stories Applied, Mike Cohn provides you with a front-to-back blueprint for writing these user stories and weaving them into your development lifecycle. You'll learn what makes a great user story, and what makes a bad one. You'll discover practical ways to gather user stories, even when you can't speak with your users. Then, once you've compiled your user stories, Cohn shows how to organize them, prioritize them, and use them for planning, management, and testing. User role modeling: understanding what users have in common, and where they differ Gathering stories: user interviewing, questionnaires, observation, and workshops Working with managers, trainers, salespeople and other "proxies" Writing user stories for acceptance testing Using stories to prioritize, set schedules, and estimate release costs Includes end-of-chapter practice questions and exercises User Stories Applied will be invaluable to every software developer, tester, analyst, and manager working with any agile method: XP, Scrum... or even your own home-grown approach.

Download or read book The Art of Agile Development written by James Shore and published by "O'Reilly Media, Inc.". This book was released on 2008 with total page 436 pages. Available in PDF, EPUB and Kindle. Book excerpt: For those considering Extreme Programming, this book provides no-nonsense advice on agile planning, development, delivery, and management taken from the authors' many years of experience. While plenty of books address the what and why of agile development, very few offer the information users can apply directly.

Download or read book Developer Testing written by Alexander Tarlinder and published by Addison-Wesley Professional. This book was released on 2016-09-07 with total page 629 pages. Available in PDF, EPUB and Kindle. Book excerpt: 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

Download or read book Continuous Integration written by Paul M. Duvall and published by Pearson Education. This book was released on 2007-06-29 with total page 313 pages. Available in PDF, EPUB and Kindle. Book excerpt: For any software developer who has spent days in “integration hell,” cobbling together myriad software components, Continuous Integration: Improving Software Quality and Reducing Risk illustrates how to transform integration from a necessary evil into an everyday part of the development process. The key, as the authors show, is to integrate regularly and often using continuous integration (CI) practices and techniques. The authors first examine the concept of CI and its practices from the ground up and then move on to explore other effective processes performed by CI systems, such as database integration, testing, inspection, deployment, and feedback. Through more than forty CI-related practices using application examples in different languages, readers learn that CI leads to more rapid software development, produces deployable software at every step in the development lifecycle, and reduces the time between defect introduction and detection, saving time and lowering costs. With successful implementation of CI, developers reduce risks and repetitive manual processes, and teams receive better project visibility. The book covers How to make integration a “non-event” on your software development projects How to reduce the amount of repetitive processes you perform when building your software Practices and techniques for using CI effectively with your teams Reducing the risks of late defect discovery, low-quality software, lack of visibility, and lack of deployable software Assessments of different CI servers and related tools on the market The book’s companion Web site, www.integratebutton.com, provides updates and code examples.

Download or read book A Practitioner s Guide to Software Test Design written by Lee Copeland and published by Artech House. This book was released on 2004 with total page 328 pages. Available in PDF, EPUB and Kindle. Book excerpt: Written by a leading expert in the field, this unique volume contains current test design approaches and focuses only on software test design. Copeland illustrates each test design through detailed examples and step-by-step instructions.

Download or read book Explore It written by Elisabeth Hendrickson and published by Pragmatic Bookshelf. This book was released on 2013-02-21 with total page 245 pages. Available in PDF, EPUB and Kindle. Book excerpt: Uncover surprises, risks, and potentially serious bugs with exploratory testing. Rather than designing all tests in advance, explorers design and execute small, rapid experiments, using what they learned from the last little experiment to inform the next. Learn essential skills of a master explorer, including how to analyze software to discover key points of vulnerability, how to design experiments on the fly, how to hone your observation skills, and how to focus your efforts. Software is full of surprises. No matter how careful or skilled you are, when you create software it can behave differently than you intended. Exploratory testing mitigates those risks. Part 1 introduces the core, essential skills of a master explorer. You'll learn to craft charters to guide your exploration, to observe what's really happening (hint: it's harder than it sounds), to identify interesting variations, and to determine what expected behavior should be when exercising software in unexpected ways. Part 2 builds on that foundation. You'll learn how to explore by varying interactions, sequences, data, timing, and configurations. Along the way you'll see how to incorporate analysis techniques like state modeling, data modeling, and defining context diagrams into your explorer's arsenal. Part 3 brings the techniques back into the context of a software project. You'll apply the skills and techniques in a variety of contexts and integrate exploration into the development cycle from the very beginning. You can apply the techniques in this book to any kind of software. Whether you work on embedded systems, Web applications, desktop applications, APIs, or something else, you'll find this book contains a wealth of concrete and practical advice about exploring your software to discover its capabilities, limitations, and risks.

Download or read book Dear Evil Tester written by Alan Richardson and published by . This book was released on 2016-03-04 with total page 148 pages. Available in PDF, EPUB and Kindle. Book excerpt: Are you in charge of your own testing? Do you have the advice you need to advance your test approach? "Dear Evil Tester" contains advice about testing that you won't hear anywhere else. "Dear Evil Tester" is a three pronged publication designed to: -provoke not placate, -make you react rather than relax, -help you laugh not languish. Starting gently with the laugh out loud Agony Uncle answers originally published in 'The Testing Planet'. "Dear Evil Tester" then provides new answers, to never before published questions, that will hit your beliefs where they change. Before presenting you with essays that will help you unleash your own inner Evil Tester. With advice on automating, communication, talking at conferences, psychotherapy for testers, exploratory testing, tools, technical testing, and more. Dear Evil Tester randomly samples the Software Testing stomping ground before walking all over it. "Dear Evil Tester" is a revolutionary testing book for the mind which shows you an alternative approach to testing built on responsibility, control and laughter. Read what our early reviewers had to say: "Wonderful stuff there. Real deep." Rob Sabourin, @RobertASabourin Author of "I Am a Bug" "The more you know about software testing, the more you will find to amuse you." Dot Graham, @dorothygraham Author of "Experiences of Test Automation" "laugh-out-loud episodes" Paul Gerrard, @paul_gerrard Author of "The Tester's Pocketbook" "A great read for every Tester." Andy Glover, @cartoontester Author of "Cartoon Tester"

Download or read book Exploratory Software Testing written by James A. Whittaker and published by Pearson Education. This book was released on 2009-08-25 with total page 475 pages. Available in PDF, EPUB and Kindle. Book excerpt: 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?