73 Results for : testable

  • Thumbnail
    Building Native Web Components
    Start developing single-page applications (SPAs) with modern architecture. This book shows you how to create, design, and publish native web components, ultimately allowing you to piece together those elements in a modern JavaScript framework.Building Native Web Components dives right in and gets you started building your first web component. You'll be introduced to native web component design systems and frameworks and discuss component-driven development to understand its importance in large-scale companies. You'll then move on to building web components using templates and APIs, and custom event lifecycles. Techniques and best practices for moving data, customizing, and distributing components are also covered. Throughout, you'll develop a foundation to start using Polymer, Vue.js, and Firebase in your day-to-day work.Confidently apply modern patterns and develop workflows to build agnostic software pieces that can be reused in SPAs. Building Native Web Components is your guide to developing small and autonomous web components that are focused, independent, reusable, testable, and works with all JavaScript frameworks, modern browsers, and libraries.What You Will LearnIncorporate component-driven development (CDD) and design systems into your workflowBuild apps with reusable UI components that are agnostic to JavaScript frameworksUtilize Polymer and Vue.js in your day-to-day workPublish your UI components in npm (Node Package Manager)Who This Book Is ForThe book is intended for Intermediate-Advanced level readers interested in single-page applications (SPAs), as well as Polymer, Vue.js, and Firebase.
    • Shop: buecher
    • Price: 35.99 EUR excl. shipping
  • Thumbnail
    The Secrets of the Seasons: You're Here for a Reason , Hörbuch, Digital, ungekürzt, 309min
    We need this book now - more than ever.Today, our Mother Earth is giving us a timeout to go to our corners and think about what we have done, and she is compelling us to wake up and to remember that we are all connected from the global markets and economies to the air we inhale and exhale.One day, we will realize that there is nothing more important in the world than knowing that each of us has a gift and that we are all here to support each other to fulfill that gift. The Secrets of the Seasons can help a sleepwalking world awaken and live a life of passion, purpose, and magic. There is an ancient yet easily testable way of bringing love and joy back into the world. We can use it to come together and shake people from their slumber while initiating a new paradigm of consciousness and capitalism, loving respect, and a better life for all. When embraced and understood, the power and simplicity of these secrets - as given to Lawrence Ford and as shared with you in this audiobook - will transform your life.By embodying the deep meaning and transformative potential these secrets have for all of our lives and by learning to make use of the upgraded big picture reality co-creation operating system that underlies this set of ancient wisdom-based road maps, we can come to live whole, in peace and prosperity, individually and collectively, as ourselves, our families, and the whole world.Like every snowflake, the special song your soul sings is completely unique to you, just as your reason for being here is unique to you. Throughout the entirety of our physical existence on Earth -through all the twists and turns on all the pathways that each of us goes down as we move through the cyclical seasons of our lives - we are guided to remember our soul’s unique song and our reason for being here.You can tune into that knowledge at any moment of your life - including right now - just as you can tune into the pure love ungekürzt. Language: English. Narrator: Benjamin McLean. Audio sample: https://samples.audible.de/bk/acx0/209746/bk_acx0_209746_sample.mp3. Digital audiobook in aax.
    • Shop: Audible
    • Price: 9.95 EUR excl. shipping
  • Thumbnail
    The Demon-Haunted World (eBook, ePUB)
    A prescient warning of a future we now inhabit, where fake news stories and Internet conspiracy theories play to a disaffected American populace "A glorious book . . . A spirited defense of science . . . From the first page to the last, this book is a manifesto for clear thought."-Los Angeles Times How can we make intelligent decisions about our increasingly technology-driven lives if we don't understand the difference between the myths of pseudoscience and the testable hypotheses of science? Pulitzer Prize-winning author and distinguished astronomer Carl Sagan argues that scientific thinking is critical not only to the pursuit of truth but to the very well-being of our democratic institutions. Casting a wide net through history and culture, Sagan examines and authoritatively debunks such celebrated fallacies of the past as witchcraft, faith healing, demons, and UFOs. And yet, disturbingly, in today's so-called information age, pseudoscience is burgeoning with stories of alien abduction, channeling past lives, and communal hallucinations commanding growing attention and respect. As Sagan demonstrates with lucid eloquence, the siren song of unreason is not just a cultural wrong turn but a dangerous plunge into darkness that threatens our most basic freedoms. Praise for The Demon-Haunted World "Powerful . . . A stirring defense of informed rationality. . . Rich in surprising information and beautiful writing."-The Washington Post Book World "Compelling."-USA Today "A clear vision of what good science means and why it makes a difference. . . . A testimonial to the power of science and a warning of the dangers of unrestrained credulity."-The Sciences "Passionate."-San Francisco Examiner-Chronicle
    • Shop: buecher
    • Price: 7.99 EUR excl. shipping
  • Thumbnail
    Domain Modeling Made Functional (eBook, ePUB)
    You want increased customer satisfaction, faster development cycles, and less wasted work. Domain-driven design (DDD) combined with functional programming is the innovative combo that will get you there. In this pragmatic, down-to-earth guide, you'll see how applying the core principles of functional programming can result in software designs that model real-world requirements both elegantly and concisely - often more so than an object-oriented approach. Practical examples in the open-source F# functional language, and examples from familiar business domains, show you how to apply these techniques to build software that is business-focused, flexible, and high quality.Domain-driven design is a well-established approach to designing software that ensures that domain experts and developers work together effectively to create high-quality software. This book is the first to combine DDD with techniques from statically typed functional programming. This book is perfect for newcomers to DDD or functional programming - all the techniques you need will be introduced and explained.Model a complex domain accurately using the F# type system, creating compilable code that is also readable documentation---ensuring that the code and design never get out of sync. Encode business rules in the design so that you have &quote;compile-time unit tests,&quote; and eliminate many potential bugs by making illegal states unrepresentable. Assemble a series of small, testable functions into a complete use case, and compose these individual scenarios into a large-scale design. Discover why the combination of functional programming and DDD leads naturally to service-oriented and hexagonal architectures. Finally, create a functional domain model that works with traditional databases, NoSQL, and event stores, and safely expose your domain via a website or API.Solve real problems by focusing on real-world requirements for your software.What You Need:The code in this book is designed to be run interactively on Windows, Mac and Linux.You will need a recent version of F# (4.0 or greater), and the appropriate .NET runtime for your platform.Full installation instructions for all platforms at fsharp.org.
    • Shop: buecher
    • Price: 28.95 EUR excl. shipping
  • Thumbnail
    Reactive Design Patterns
    SummaryReactive Design Patterns is a clearly written guide for building message-driven distributed systems that are resilient, responsive, and elastic. In this book you'll find patterns for messaging, flow control, resource management, and concurrency, along with practical issues like test-friendly designs. All patterns include concrete examples using Scala and Akka. Foreword by Jonas Bonér. Purchase of the print book includes a free eBook in PDF, Kindle, and ePub formats from Manning Publications.About the TechnologyModern web applications serve potentially vast numbers of users - and they need to keep working as servers fail and new ones come online, users overwhelm limited resources, and information is distributed globally. A Reactive application adjusts to partial failures and varying loads, remaining responsive in an ever-changing distributed environment. The secret is message-driven architecture - and design patterns to organize it.About the BookReactive Design Patterns presents the principles, patterns, and best practices of Reactive application design. You'll learn how to keep one slow component from bogging down others with the Circuit Breaker pattern, how to shepherd a many-staged transaction to completion with the Saga pattern, how to divide datasets by Sharding, and more. You'll even see how to keep your source code readable and the system testable despite many potential interactions and points of failure. What's InsideThe definitive guide to the Reactive ManifestoPatterns for flow control, delimited consistency, fault tolerance, and much moreHard-won lessons about what doesn't workArchitectures that scale under tremendous loadAbout the ReaderMost examples use Scala, Java, and Akka. Readers should be familiar with distributed systems.About the AuthorDr. Roland Kuhn led the Akka team at Lightbend and coauthored the Reactive Manifesto. Brian Hanafee and Jamie Allen are experienced distributed systems architects. Table of ContentsPART 1 - INTRODUCTIONWhy Reactive? A walk-through of the Reactive Manifesto Tools of the trade PART 2 - THE PHILOSOPHY IN A NUTSHELLMessage passing Location transparency Divide and conquer Principled failure handling Delimited consistency Nondeterminism by need Message flow PART 3 - PATTERNS Testing reactive applications Fault tolerance and recovery patterns Replication patterns Resource-management patterns Message flow patterns Flow control patterns State management and persistence patterns
    • Shop: buecher
    • Price: 36.99 EUR excl. shipping
  • Thumbnail
    Modern Data Engineering with Apache Spark
    Leverage Apache Spark within a modern data engineering ecosystem. This hands-on guide will teach you how to write fully functional applications, follow industry best practices, and learn the rationale behind these decisions. With Apache Spark as the foundation, you will follow a step-by-step journey beginning with the basics of data ingestion, processing, and transformation, and ending up with an entire local data platform running Apache Spark, Apache Zeppelin, Apache Kafka, Redis, MySQL, Minio (S3), and Apache Airflow.Apache Spark applications solve a wide range of data problems from traditional data loading and processing to rich SQL-based analysis as well as complex machine learning workloads and even near real-time processing of streaming data. Spark fits well as a central foundation for any data engineering workload. This book will teach you to write interactive Spark applications using Apache Zeppelin notebooks, write and compile reusable applications and modules, and fully test both batch and streaming. You will also learn to containerize your applications using Docker and run and deploy your Spark applications using a variety of tools such as Apache Airflow, Docker and Kubernetes.Reading this book will empower you to take advantage of Apache Spark to optimize your data pipelines and teach you to craft modular and testable Spark applications. You will create and deploy mission-critical streaming spark applications in a low-stress environment that paves the way for your own path to production.What You Will LearnSimplify data transformation with Spark Pipelines and Spark SQLBridge data engineering with machine learningArchitect modular data pipeline applications Build reusable application components and libraries Containerize your Spark applications for consistency and reliabilityUse Docker and Kubernetes to deploy your Spark applicationsSpeed up application experimentation using Apache Zeppelin and Docker Understand serializable structured data and data contracts Harness effective strategies for optimizing data in your data lakes Build end-to-end Spark structured streaming applications using Redis and Apache Kafka Embrace testing for your batch and streaming applications Deploy and monitor your Spark applications Who This Book Is ForProfessional software engineers who want to take their current skills and apply them to new and exciting opportunities within the data ecosystem, practicing data engineers who are looking for a guiding light while traversing the many challenges of moving from batch to streaming modes, data architects who wish to provide clear and concise direction for how best to harness and use Apache Spark within their organization, and those interested in the ins and outs of becoming a modern data engineer in today's fast-paced and data-hungry world
    • Shop: buecher
    • Price: 52.99 EUR excl. shipping
  • Thumbnail
    Modern Data Engineering with Apache Spark (eBook, PDF)
    Leverage Apache Spark within a modern data engineering ecosystem. This hands-on guide will teach you how to write fully functional applications, follow industry best practices, and learn the rationale behind these decisions. With Apache Spark as the foundation, you will follow a step-by-step journey beginning with the basics of data ingestion, processing, and transformation, and ending up with an entire local data platform running Apache Spark, Apache Zeppelin, Apache Kafka, Redis, MySQL, Minio (S3), and Apache Airflow. Apache Spark applications solve a wide range of data problems from traditional data loading and processing to rich SQL-based analysis as well as complex machine learning workloads and even near real-time processing of streaming data. Spark fits well as a central foundation for any data engineering workload. This book will teach you to write interactive Spark applications using Apache Zeppelin notebooks, write and compile reusable applications and modules, and fully test both batch and streaming. You will also learn to containerize your applications using Docker and run and deploy your Spark applications using a variety of tools such as Apache Airflow, Docker and Kubernetes.¿Reading this book will empower you to take advantage of Apache Spark to optimize your data pipelines and teach you to craft modular and testable Spark applications. You will create and deploy mission-critical streaming spark applications in a low-stress environment that paves the way for your own path to production. ¿ What You Will LearnSimplify data transformation with Spark Pipelines and Spark SQL Bridge data engineering with machine learningArchitect modular data pipeline applications Build reusable application components and libraries Containerize your Spark applications for consistency and reliabilityUse Docker and Kubernetes to deploy your Spark applications Speed up application experimentation using Apache Zeppelin and Docker Understand serializable structured data and data contracts Harness effective strategies for optimizing data in your data lakes Build end-to-end Spark structured streaming applications using Redis and Apache Kafka Embrace testing for your batch and streaming applications Deploy and monitor your Spark applications Who This Book Is For Professional software engineers who want to take their current skills and apply them to new and exciting opportunities within the data ecosystem, practicing data engineers who are looking for a guiding light while traversing the many challenges of moving from batch to streaming modes, data architects who wish to provide clear and concise direction for how best to harness and use Apache Spark within their organization, and those interested in the ins and outs of becoming a modern data engineer in today's fast-paced and data-hungry world
    • Shop: buecher
    • Price: 40.95 EUR excl. shipping
  • Thumbnail
    User Stories Applied
    Learn to build robust software that more closely meets the customer's needs through applying the concept of user stories. A clear explanation of the most agile means of gathering software requirements Thoroughly reviewed and eagerly anticipated by the agile software development community Allows the reader to save time and resources by gathering the proper requirements BEFORE coding begins The concept of user stories has its roots as one of the main tenets of Extreme Programming. In simple terms, user stories represent an effective means of gathering requirements from the customer (roughly akin to use cases). This book describes user stories and demonstrates how they can be used to properly plan, manage, and test software development projects. The book highlights both successful and unsuccessful implementations of the concept, and provides sets of questions and exercises that drive home its main points. After absorbing the lessons in this book, readers will be able to introduce user stories in their organizations as an effective means of determining precisely what is required of a software application. Product Description 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. Features + Benefits Learn to build robust software that more closely meets the customer's needs through applying the concept of user stories. ° A clear explanation of the most agile means of gathering software requirements ° Thoroughly reviewed and eagerly anticipated by the agile software development community ° Allows the reader to save time and resources by gathering the proper requirements BEFORE coding begins Backcover Agile requirements: discovering what your users really want. With this book, you will learn to: Flexible, quick and practical requirements that work Save time and develop better software that meets users' needs Gathering user stories -- even when you can't talk to users How user stories work, and how they differ from use cases, scenarios, and traditional requirements Leveraging user stories as part of planning, scheduling, estimating, and testing Ideal for Extreme Programming, Scrum, or any other agile methodology ---------------------------------------------------------------------------------------------------------- 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. ADDISON-WESLEY PROFESSIONAL Boston, MA 02116 www.awprofessional.com ISBN: 0-321-20568-5 Foreword. Acknowledgments. Introduction. I: GETTING STARTED. 1: An Overview. What Is a User Story? Where Are the Details? "How Long Does It Have to Be?" The Customer Team. What Will the Process Be Like? Planning Releases and Iterations. What Are Acceptance Tests? Why Change? Summary. Questions. 2: Writing Stories. Independent. Negotiable. Valuable to Purchasers or Users. Estimatable. Small. Testable. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 3: User Role Modeling. User Roles. Role Modeling Steps. Two Additional Techniques. What If I Have On-Site Users? Summary. Developer Responsibilities. Customer Responsibilities. Questions. 4: Gathering Stories. Elicitation and Capture Should Be Illicit. A Little Is Enough, or Is It? Techniques. User Interviews. Questionnaires. Observation. Story-Writing Workshops. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 5: Working with User Proxies. The Users' Manager. A Development Manager. Salespersons. Domain Experts. The Marketing Group. Former Users. Customers. Trainers and Technical Support. Business or Systems Analysts. What to Do When Working with a User Proxy. Can You Do It Yourself? Constituting the Customer Team. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 6: Acceptance Testing User Stories. Write Tests Before Coding. The Customer Specifies the Tests. Testing Is Part of the Process. How Many Tests Are Too Many? The Framework for Integrated Test. Types of Testing. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 7: Guidelines for Good Stories. Start with Goal Stories. Slice the Cake. Write Closed Stories. Put Constraints on Cards. Size the Story to the Horizon. Keep the UI Out as Long as Possible. Some Things Aren't Stories. Include User Roles in the Stories. Write for One User. Write in Active Voice. Customer Writes. Don't Number Story Cards. Don't Forget the Purpose. Summary. Questions. II: ESTIMATING AND PLANNING. 8: Estimating User Stories. Story Points. Estimate as a Team. Estimating. Triangulate. Using Story Points. What If We Pair Program? Some Reminders. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 9: Planning a Release. When Do We Want the Release? What Would You Like in It? Prioritizing the Stories. Mixed Priorities. Risky Stories. Prioritizing Infrastructural Needs. Selecting an Iteration Length. From Story Points to Expected Duration. The Initial Velocity. Creating the Release Plan. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 10: Planning an Iteration. Iteration Planning Overview. Discussing the Stories. Disaggregating into Tasks. Accepting Responsibility. Estimate and Confirm. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 11: Measuring and Monitoring Velocity. Measuring Velocity. Planned and Actual Velocity. Iteration Burndown Charts. Burndown Charts During an Iteration. Summary. Developer Responsibilities. Customer Responsibilities. Questions. III: FREQUENTLY DISCUSSED TOPICS. 12: What Stories Are Not. User Stories Aren't IEEE 830. User Stories Are Not Use Cases. User Stories Aren't Scenarios. Summary. Questions. 13: Why User Stories? Verbal Communication. User Stories Are Comprehensible. User Stories Are the Right Size for Planning. User Stories Work for Iterative Development. Stories Encourage Deferring Detail. Stories Support Opportunistic Development. User Stories Encourage Participatory Design. Stories Build Up Tacit Knowledge. Why Not Stories? Summary. Developer Responsibilities. Customer Responsibilities. Questions. 14: A Catalog of Story Smells. Stories Are Too Small. Interdependent Stories. Goldplating. Too Many Details. Including User Interface Detail Too Soon. Thinking Too Far Ahead. Splitting Too Many Stories. Customer Has Trouble Prioritizing. Customer Won't Write and Prioritize the Stories. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 15: Using Stories with Scrum. Scrum Is Iterative and Incremental. The Basics of Scrum. The Scrum Team. The Product Backlog. The Sprint Planning Meeting. The Sprint Review Meeting. The Daily Scrum Meeting. Adding Stories to Scrum. A Case Study. Summary. Questions. 16: Additional Topics. Handling NonFunctional Requirements. Paper or Software? User Stories and the User Interface. Retaining the Stories. Stories for Bugs. Summary. Developer Responsibilities. Customer Responsibilities. Questions. IV: AN EXAMPLE. 17: The User Roles. The Project. Identifying the Customer. Identifying Some Initial Roles. Consolidating and Narrowing. Role Modeling. Adding Personas. 18: The Stories. Stories for Teresa. Stories for Captain Ron. Stories for a Novice Sailor. Stories for a Non-Sailing Gift Buyer. Stories for a Report Viewer. Some Administration Stories. Wrapping Up. 19: Estimating the Stories. The First Story. Advanced Search. Rating and Reviewing. Accounts. Finishing the Estimates. All the Estimates. 20: The Release Plan. Estimating Velocity. Prioritizing the Stories. The Finished Release Plan. 21: The Acceptance Tests.The concept of user stories has its roots as one of the main tenets of ExtremeProgramming. In simple terms, user stories represent an effective means ofgathering requirements from the customer (roughly akin to use cases). Thisbook describes user stories and demonstrates how they can be used to properlyplan, manage, and test software development projects. The book highlightsboth successful and unsuccessful implementations of the concept, and providessets of questions and exercises that drive home its main points. After absorbingthe lessons in this book, readers will be able to introduce user stories in theirorganizations as an effective means of determining precisely what is required ofa software application.
    • Shop: buecher
    • Price: 31.99 EUR excl. shipping
  • Thumbnail
    Agile Testing
    "As Agile methods have entered the mainstream, we've learned a lot about how the testing discipline fits into Agile projects. Lisa and Janet give us a solid look at what to do, and what to avoid, in Agile testing." -Ron Jeffries, www.XProgramming.com "An excellent introduction to agile and how it affects the software test community!" -Gerard Meszaros, Agile Practice Lead and Chief Test Strategist at Solution Frameworks, Inc., an agile coaching and lean software development consultancy "In sports and music, people know the importance of practicing technique until it becomes a part of the way they do things. This book is about some of the most fundamental techniques in software development-how to build quality into code-techniques that should become second nature to every development team. The book provides both broad and in-depth coverage of how to move testing to the front of the development process, along with a liberal sprinkling of real-life examples that bring the book to life." -Mary Poppendieck, Author of Lean Software Development and Implementing Lean Software Development "Refreshingly pragmatic. Chock-full of wisdom. Absent of dogma. This book is a gamechanger. Every software professional should read it." -Uncle Bob Martin, Object Mentor, Inc. "With Agile Testing, Lisa and Janet have used their holistic sensibility of testing to describe a culture shift for testers and teams willing to elevate their test effectiveness. The combination of real-life project experiences and specific techniques provide an excellent way to learn and adapt to continually changing project needs." -Adam Geras, M.Sc. Developer-Tester, Ideaca Knowledge Services "On Agile projects, everyone seems to ask, 'But, what about testing?' Is it the development team's responsibility entirely, the testing team, or a collaborative effort between developers and testers? Or, 'How much testing should we automate?' Lisa and Janet have written a book that finally answers these types of questions and more! Whether you're a tester, developer, or manager, you'll learn many great examples and stories from the real-world work experiences they've shared in this excellent book." -Paul Duvall, CTO of Stelligent and co-author of Continuous Integration: Improving Software Quality and Reducing Risk "Finally a book for testers on Agile teams that acknowledges there is not just one right way! Agile Testing provides comprehensive coverage of the issues testers face when they move to Agile: from tools and metrics to roles and process. Illustrated with numerous stories and examples from many contributors, it gives a clear picture of what successful Agile testers are doing today." -Bret Pettichord, Chief Technical Officer of WatirCraft and Lead Developer of Watir Testing is a key component of agile development. The widespread adoption of agile methods has brought the need for effective testing into the limelight, and agile projects have transformed the role of testers. Much of a tester's function, however, remains largely misunderstood. What is the true role of a tester? Do agile teams actually need members with QA backgrounds? What does it really mean to be an "agile tester?" Two of the industry's most experienced agile testing practitioners and consultants, Lisa Crispin and Janet Gregory, have teamed up to bring you the definitive answers to these questions and many others. In Agile Testing, 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. Readers will come away from this book understanding How to get testers engaged in agile development Where testers and QA managers fit on an agile team What to look for when hiring an agile tester How to transition from a traditional cycle to agile development How to complete testing activities in short iterations How to use tests to successfully guide development How to overcome barriers to test automation This book is a must for agile testers, agile teams, their managers, and their customers. Product Description Te>Two of the industry’s most experienced agile testing practitioners and consultants, Lisa Crispin and Janet Gregory, have teamed up to bring you the definitive answers to these questions and many others. In Agile Testing, 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.Readers will come away from this book understandingHow to get testers engaged in agile development Where testers and QA managers fit on an agile team What to look for when hiring an agile tester How to transition from a traditional cycle to agile development How to complete testing activities in short iterations How to use tests to successfully guide development How to overcome barriers to test automation This book is a must for agile testers, agile teams, their managers, and their customers. The eBook edition of Agile Testing also is available as part of a two-eBook collection, The Agile Testing Collection (9780134190624). Backcover Testing is a key component of agile development. The widespread adoption of agile methods has brought the need for effective testing into the limelight, and agile projects have transformed the role of testers. Much of a tester's function, however, remains largely misunderstood. What is the true role of a tester? Do agile teams actually need members with QA backgrounds? What does it really mean to be an "agile tester?" Two of the industry's most experienced agile testing practitioners and consultants, Lisa Crispin and Janet Gregory, have teamed up to bring you the definitive answers to these questions and many others. In Agile Testing, 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. Readers will come away from this book understanding How to get testers engaged in agile development Where testers and QA managers fit on an agile team What to look for when hiring an agile tester How to transition from a traditional cycle to agile development How to complete testing activities in short iterations How to use tests to successfully guide development How to overcome barriers to test automation This book is a must for agile testers, agile teams, their managers, and their customers. Foreword by Mike Cohn xxiii Foreword by Brian Marick xxv Preface xxvii Acknowledgments xxxvii About the Authors xli Part I: Introduction 1 Chapter 1: What Is Agile Testing, Anyway? 3 Agile Values 3 What Do We Mean by "Agile Testing"? 4 A Little Context for Roles and Activities on an Agile Team 7 How Is Agile Testing Different? 9 Whole-Team Approach 15 Summary 17 Chapter 2: Ten Principles for Agile Testers 19 What's an Agile Tester? 19 The Agile Testing Mind-Set 20 Applying Agile Principles and Values 21 Adding Value 31 Summary 33 Part II: Organizational Challenges 35 Chapter 3: Cultural Challenges 37 Organizational Culture 37 Barriers to Successful Agile Adoption by Test/QA Teams 44 Introducing Change 49 Management Expectations 52 Change Doesn't Come Easy 56 Summary 58 Chapter 4: Team Logistics 59 Team Structure 59 Physical Logistics 65 Resources 66 Building a Team 69 Summary 71 Chapter 5: Transitioning Typical Processes 73 Seeking Lightweight Processes 73 Metrics 74 Defect Tracking 79 Test Planning 86 Existing Processes and Models 88 Summary 93 Part III: The Agile Testing Quadrants 95 Chapter 6: The Purpose of Testing 97 The Agile Testing Quadrants 97 Knowing When a Story Is Done 104 Managing Technical Debt 106 Testing in Context 106 Summary 108 Chapter 7: Technology-Facing Tests that Support the Team 109 An Agile Testing Foundation 109 Why Write and Execute These Tests? 112 Where Do Technology-Facing Tests Stop? 119 What If the Team Doesn't Do These Tests? 121 Toolkit 123 Summary 127 Chapter 8: Business-Facing Tests that Support the Team 129 Driving Development with Business-Facing Tests 129 The Requirements Quandary 132 Thin Slices, Small Chunks 144 How Do We Know We're Done? 146 Tests Mitigate Risk 147 Testability and Automation 149 Summary 150 Chapter 9: Toolkit for Business-Facing Tests that Support the Team 153 Business-Facing Test Tool Strategy 153 Tools to Elicit Examples and Requirements 155 Tools for Automating Tests Based on Examples 164 Strategies for Writing Tests 177 Testability 183 Test Management 186 Summary 186 Chapter 10: Business-Facing Tests that Critique the Product 189 Introduction to Quadrant 3 190 Demonstrations 191 Scenario Testing 192 Exploratory Testing 195 Usability Testing 202 Behind the GUI 204 Testing Documents and Documentation 207 Tools to Assist with Exploratory Testing 210 Summary 214 Chapter 11: Critiquing the Product Using Technology-Facing Tests 217 Introduction to Quadrant 4 217 Who Does It? 220 When Do You Do It? 222 "ility" Testing 223 Performance, Load, Stress, and Scalability Testing 233 Summary 238 Chapter 12: Summary of Testing Quadrants 241 Review of the Testing Quadrants 241 A System Test Example 242 Tests Driving Development 244 Automation 245 Critiquing the Product with Business-Facing Tests 248 Documentation 251 Using the Agile Testing Quadrants 252 Summary 253 Part IV: Automation 255 Chapter 13: Why We Want to Automate Tests and What Holds Us Back 257 Why Automate? 258 Barriers to Automation-Things that Get in the Way 264 Can We Overcome These Barriers? 270 Summary 271 Chapter 14: An Agile Test Automation Strategy 273 An Agile Approach to Test Automation 274 What Can We Automate? 279 What Shouldn't We Automate? 285 What Might Be Hard to Automate? 287 Developing an Automation Strategy-Where Do We Start? 288 Applying Agile Principles to Test Automation 298 Supplying Data for Tests 304 Evaluating Automation Tools 311 Implementing Automation 316 Managing Automated Tests 319 Go Get Started 324 Summary 324 Part V: An Iteration in the Life of a Tester 327 Chapter 15: Tester Activities in Release or Theme Planning 329 The Purpose of Release Planning 330 Sizing 332 Prioritizing 338 What's in Scope? 340 Test Planning 345 Test Plan Alternatives 350 Preparing for Visibility 354 Summary 366 Chapter 16: Hit the Ground Running 369 Be Proactive 369 Advance Clarity 373 Examples 378 Test Strategies 380 Prioritize Defects 381 Resources 381 Summary 382 Chapter 17: Iteration Kickoff 383 Iteration Planning 383 Testable Stories 393 Collaborate with Customers 396 High-Level Tests and Examples 397 Summary 403 Chapter 18: Coding and Testing 405 Driving Development 406 Tests that Critique the Product 412 Collaborate with Programmers 413 Talk to Customers 414 Completing Testing Tasks 415 Dealing with Bugs 416 It's All about Choices 419 Facilitate Communication 429 Regression Tests 432 Resources 434 Iteration Metrics 435 Summary 440 Chapter 19: Wrap Up the Iteration 443 Iteration Demo 443 Retrospectives 444 Celebrate Successes 449 Summary 451 Chapter 20: Successful Delivery 453 What Makes a Product? 453 Planning Enough Time for Testing 455 The End Game 456 Customer Testing 464 Post-Development Testing Cycles 467 Deliverables 468 Releasing the Product 470 Customer Expectations 475 Summary 476 Part VI: Summary 479 Chapter 21: Key Success Factors 481 Success Factor 1: Use the Whole-Team Approach 482 Success Factor 2: Adopt an Agile Testing Mind-Set 482 Success Factor 3: Automate Regression Testing 484 Success Factor 4: Provide and Obtain Feedback 484 Success Factor 5: Build a Foundation of Core Practices 486 Success Factor 6: Collaborate with Customers 489 Success Factor 7: Look at the Big Picture 490 Summary 491 Glossary 493 Bibliography 501 Index 509 Testing is a key component of agile development. The widespread adoption of agile methods has brought the need for effective testing into the limelight, and agile projects have transformed the role of testers. Much of a tester's function, however, remains largely misunderstood. What is the true role of a tester? Do agile teams actually need members with QA backgrounds? What does it really mean to be an "agile tester?" Two of the industry's most experienced agile testing practitioners and consultants, Lisa Crispin and Janet Gregory, have teamed up to bring you the definitive answers to these questions and many others. In Agile Testing, 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.Readers will come away from this book understandingHow to get testers engaged in agile development Where testers and QA managers fit on an agile team What to look for when hiring an agile tester How to transition from a traditional cycle to agile development How to complete testing activities in short iterations How to use tests to successfully guide development How to overcome barriers to test automationThis book is a must for agile testers, agile teams, their managers, and their customers.
    • Shop: buecher
    • Price: 34.99 EUR excl. shipping
  • Thumbnail
    Digital System Test and Testable Design
    Digital System Test and Testable Design - Using HDL Models and Architectures. Auflage 2011: ab 106.99 €
    • Shop: ebook.de
    • Price: 106.99 EUR excl. shipping

Similar searches: