Who should read *Agile Testing: A Practical Guide for Testers and Agile Teams*?

This book is ideal for: - Testers adapting to agile environments. - QA managers navigating organizational shifts to agile. - Developers seeking to improve collaboration with testers. - Scrum masters or coaches addressing testing bottlenecks. It answers questions like *“What do testers do if developers write tests?”* and *“How to handle load testing in short iterations?”*

Is *Agile Testing* by Lisa Crispin worth reading?

Yes, it’s a seminal resource for agile teams, blending theory with pratical advice. The book’s use of Brian Marick’s Agile Testing Matrix helps teams categorize tests (business-facing vs. technology-facing) and prioritize efforts. Over 20 chapters offer solutions for test automation, iteration planning, and overcoming cultural barriers in transitioning organizations.

What is the Agile Testing Matrix in *Agile Testing*?

The Agile Testing Matrix, introduced by Brian Marick, categorizes testing into four quadrants: 1. **Business-facing tests** guiding development. 2. **Technology-facing tests** critiquing the product. 3. **User acceptance tests**. 4. **Non-functional tests** (performance, security). This framework helps teams align testing activities with project goals and stakeholder needs.

How does *Agile Testing* address test automation challenges?

The book identifies common barriers like flaky tests and inadequate tooling, offering strategies such as incremental automation and collaboration between developers/testers. It emphasizes building a maintainable automation suite that supports continuous integration, with examples of teams balancing unit tests, API tests, and UI validation.

What organizational challenges does *Agile Testing* cover?

Key challenges include: - Cultural resistance to shifting testing left. - Aligning metrics with agile values (e.g., prioritizing defects by business impact). - Revamping defect tracking systems for iterative workflows. Case studies show how teams adapted roles, reduced documentation overhead, and integrated testers into cross-functional teams.

How does *Agile Testing* compare to traditional testing guides?

Unlike traditional guides focused on phase-gate processes, this book emphasizes continuous testing integrated into agile cycles. It redefines testers as “quality coaches” who facilitate collaboration, automate repetitive checks, and use exploratory testing to uncover risks early. Real-life stories illustrate how teams replaced rigid test plans with adaptive strategies.

What are key success factors for agile testers according to the book?

Critical factors include: - Adopting a “whole-team” ownership of quality. - Leveraging face-to-face communication to clarify requirements. - Using lightweight documentation like checklists. - Prioritizing feedback loops through CI/CD pipelines. The authors stress mindset shifts over tools, advocating for curiosity and adaptability.

Pruebas ágiles

Q: What is *Agile Testing: A Practical Guide for Testers and Agile Teams* about?

*Agile Testing* by Lisa Crispin and Janet Gregory provides actionable strategies for integrating testing into agile workflows. It explains how testers, developers, and managers can collaborate to deliver high-quality software through real-world examples, the Agile Testing Matrix, and test automation solutions. The book addresses challenges like transitioning from waterfall methodologies, automating tests effectively, and balancing iterative development with comprehensive testing.

Una guía práctica para testers y equipos ágiles

Lisa Crispin

3.82(1114 Reviews)

Resumen de Pruebas ágiles

Revolucionando la calidad del software, "Agile Testing" transformó la forma en que trabajan los equipos de desarrollo al introducir el marco de los Cuadrantes de Pruebas, que ahora es el estándar. Los líderes de la industria lo citan como una lectura esencial, que ha redefinido la manera en que las empresas entregan software. ¿Alguna vez se ha preguntado por qué la tecnología moderna avanza tan rápido sin romperse? Este libro inició esa revolución.

Elige cómo se cuenta

Un libro. Muchas formas de escucharlo.

Las mismas ideas de Pruebas ágiles. Elige la voz, profundidad y ritmo que más te convengan. Cambia cuando quieras.

Capítulo 1

Transforming Quality: The Revolution of Agile Testing

Imagine a world where software quality isn't something tacked on at the end of development but woven into its very fabric. A world where testers aren't the "quality police" but valued collaborators who guide development from day one. This isn't a fantasy-it's the reality that Lisa Crispin and Janet Gregory present in their groundbreaking work "Agile Testing." Since its publication, this book has become the definitive guide for quality professionals navigating the agile landscape, endorsed by luminaries like "Uncle Bob" Martin and Mary Poppendieck. Its influence extends beyond testing circles-it's shaped how entire organizations approach quality in the digital age, fundamentally changing the relationship between those who build software and those who test it.

Capítulo 2

The Whole-Team Approach to Quality

Traditional software development created artificial barriers between developers and testers, often positioning testers as gatekeepers who would "catch" bugs after development was complete. This adversarial relationship was not only inefficient but fundamentally flawed. In agile testing, quality becomes everyone's responsibility-not just designated testers. The whole-team approach means that while team members may have specialized skills, everyone contributes to quality. Developers write automated unit tests and participate in acceptance testing. Testers may help write test-driven code or pair with programmers. Business analysts might write acceptance tests alongside testers. This collaborative approach leverages diverse perspectives to deliver better software. What makes this approach powerful is the recognition that quality can't be "tested in" at the end of development. Instead, it must be built in from the beginning through continuous testing, feedback, and improvement. As Crispin and Gregory emphasize, "Quality is not a department; it's a mindset." The benefits of this approach are substantial. Teams experience fewer defects, faster delivery cycles, and improved morale. When quality is everyone's job, there's no finger-pointing when issues arise-just collaborative problem-solving. One team Crispin worked with reduced their defect rate by 80% within six months of adopting the whole-team approach, while simultaneously increasing their delivery velocity. This cultural shift requires letting go of traditional roles and embracing new ways of working together. Testers must abandon the "quality police" mentality and become facilitators who help the team deliver the best possible product. Developers must recognize that writing testable code is as important as writing functional code. Product owners must participate actively in defining acceptance criteria and reviewing test results. The whole-team approach doesn't diminish the value of testing expertise-it amplifies it by distributing it throughout the team while still recognizing the unique perspective testers bring to the table.

Ve cada palabra mientras la escuchas

Sigue la lectura sin esfuerzo mientras cada palabra de Pruebas ágiles se ilumina en tiempo real.

Capítulo 3

The Agile Testing Mindset

Success in agile testing requires more than just following practices-it demands embracing a fundamentally different mindset. This mindset values collaboration over gatekeeping, prevention over detection, and learning over blame. The agile testing mindset begins with courage-the willingness to speak up when you see problems, to ask questions that might seem obvious, and to admit when you don't know something. In traditional environments, testers often fear being blamed for "missing bugs" or delaying releases. In agile teams, testers must have the courage to raise concerns early, even when it's uncomfortable. Consider the tester who notices that a new feature might cause problems for users with disabilities. In a traditional environment, they might document this in a defect report and hope it gets prioritized. With an agile testing mindset, they immediately bring the team together, demonstrate the issue, and collaborate on a solution before the code is even committed. This mindset also embraces continuous improvement. Agile testers constantly seek better ways to work-experimenting with new tools, learning automation skills, and studying the business domain. They recognize that yesterday's testing approach may not be sufficient for tomorrow's challenges. Perhaps most importantly, the agile testing mindset focuses on delivering value rather than following processes. Testers ask: "How can I help the team deliver what the customer really needs?" rather than "Did we follow the test plan?" This value-centered approach means sometimes breaking from conventional testing wisdom when it serves the project's goals. The shift to an agile testing mindset can be challenging. Many testers have been trained to think in terms of comprehensive test plans, detailed documentation, and rigorous processes. The agile approach-with its emphasis on adaptation, collaboration, and just-enough documentation-can feel chaotic at first. But those who make the transition discover a more engaging and effective way to ensure quality.

Capítulo 4

The Four Quadrants of Agile Testing

One of the most valuable frameworks introduced in "Agile Testing" is the Agile Testing Quadrants, which helps teams ensure they're considering all necessary types of testing. This model, originally conceived by Brian Marick and expanded by Crispin and Gregory, organizes tests along two dimensions: whether they support the team or critique the product, and whether they're business-facing or technology-facing. Quadrant 1 (Q1) contains technology-facing tests that support the team-primarily unit and component tests. These tests guide development through practices like Test-Driven Development (TDD), ensuring code works as intended at the most granular level. They provide rapid feedback to developers and create a safety net for refactoring. Without solid Q1 testing, teams struggle to maintain velocity as their codebase grows. Quadrant 2 (Q2) includes business-facing tests that support the team-primarily functional tests that verify the system meets business requirements. These tests, often written in collaboration with business stakeholders, serve as executable specifications that guide development. They answer the question: "Are we building the right thing?" Tools like FitNesse, Cucumber, or SpecFlow help capture these tests in business language while making them executable. Quadrant 3 (Q3) encompasses business-facing tests that critique the product-including exploratory testing, usability testing, and user acceptance testing. These tests evaluate the system from the user's perspective, often revealing issues that automated tests miss. They require human judgment and creativity, focusing on how the product will actually be used rather than just whether it meets specifications. Quadrant 4 (Q4) contains technology-facing tests that critique the product-including performance, security, and reliability testing. These tests verify non-functional requirements that users may not explicitly request but are essential for a successful product. They often require specialized tools and expertise. The quadrants aren't sequential steps-teams typically work in multiple quadrants simultaneously. However, they help ensure comprehensive testing coverage and appropriate test automation. Most importantly, they remind teams that different types of testing serve different purposes and require different approaches. For example, a team developing a financial application might use JUnit tests (Q1) to verify calculation logic, Cucumber scenarios (Q2) to confirm business rules are implemented correctly, exploratory testing (Q3) to evaluate the user experience, and load testing tools (Q4) to ensure the system can handle peak transaction volumes. Understanding these quadrants helps teams avoid common pitfalls like over-automating Q3 tests (which require human judgment) or neglecting Q4 tests until it's too late to address performance issues. It also helps testers communicate more effectively about different testing activities and their purposes.

Saca más partido a Pruebas ágiles

Recibe ideas a diario de más de 100 mil lecciones
Las palabras se iluminan al ritmo del audio
Tu biblioteca guardada en todos tus dispositivos

Capítulo 5

Driving Development with Tests

In agile development, tests don't just verify that code works-they drive the development process itself. This concept, central to practices like Test-Driven Development (TDD) and Behavior-Driven Development (BDD), represents a fundamental shift in how software is created. The process begins before a single line of code is written. Business stakeholders, developers, and testers collaborate to define examples that illustrate how the system should behave. These examples become the acceptance criteria for user stories and eventually evolve into automated tests. For instance, when developing an online shopping cart, the team might start with examples like: "When a user adds a $20 item to their cart, the subtotal should be $20" or "When a user applies a 10% discount code to a $20 item, the total should be $18." These examples clarify requirements and expose assumptions before coding begins. Developers then write unit tests that express these requirements at a technical level before implementing the actual code. This "test-first" approach ensures that code is designed for testability and meets the defined requirements. It also provides immediate feedback when changes break existing functionality. The benefits of this approach are substantial. Requirements become more concrete and less ambiguous. Code quality improves because it's designed to be testable from the beginning. The team builds only what's needed rather than implementing speculative features. And perhaps most importantly, automated tests serve as living documentation that evolves with the code. However, driving development with tests requires discipline and collaboration. Developers must resist the temptation to jump straight into coding without first clarifying requirements through tests. Testers must learn to express requirements as testable examples rather than abstract descriptions. Business stakeholders must participate actively in defining and reviewing tests. Teams that master this approach find that it fundamentally changes how they work. Testing becomes a design activity rather than just verification. Quality becomes a continuous concern rather than an end-stage check. And the entire team develops a shared understanding of what they're building and why.

Capítulo 6

The Automation Pyramid

Test automation is essential for agile teams, but not all tests should be automated in the same way. The test automation pyramid, described by Crispin and Gregory, provides a strategic approach to test automation that maximizes return on investment. The pyramid has three layers, with the largest at the bottom: 1. Unit and component tests (the foundation): These tests are numerous, quick to run, and focused on small pieces of functionality. They provide rapid feedback to developers and catch issues early when they're cheapest to fix. Teams should invest heavily in this layer, automating thousands of unit tests that run in minutes. 2. API and service tests (the middle): These tests operate at the business logic level, bypassing the user interface to test functionality directly. They're more stable than UI tests because they're not affected by cosmetic changes, and they run faster because they don't require browser rendering. This layer should contain hundreds of tests that verify business rules and integration points. 3. UI tests (the top): These tests interact with the application through its user interface, simulating actual user behavior. They're valuable for verifying end-to-end workflows but are also the most fragile and slowest to run. Teams should be selective about what they automate at this level, focusing on critical paths rather than trying to cover every possible scenario. Patrick Wilson-Welsh adds a memorable metaphor to this pyramid, comparing the bottom layer to brick (solid and stable), the middle layer to sticks (occasionally needing rearrangement), and the top layer to straw (fragile and easily broken). Many teams struggle with an "inverted pyramid"-too many UI tests and too few unit tests. This approach leads to slow, brittle test suites that provide delayed feedback and require constant maintenance. By rebalancing their automation efforts according to the pyramid, teams can achieve faster feedback, more reliable tests, and better coverage. Implementing this strategy requires collaboration between developers and testers. Developers typically take primary responsibility for unit tests, while testers may focus more on API and UI tests. However, the whole-team approach means that everyone contributes to the automation strategy and helps maintain the test suite. The automation pyramid isn't just about efficiency-it's about creating a sustainable testing practice that can evolve with the application. When teams invest appropriately at each level, they build a foundation for continuous delivery and can confidently make changes knowing their tests will catch regressions quickly.

Ve cada palabra mientras la escuchas

Sigue la lectura sin esfuerzo mientras cada palabra de Pruebas ágiles se ilumina en tiempo real.

Capítulo 7

The Tester's Role in Agile Teams

In agile teams, testers play a multifaceted role that extends far beyond finding bugs. They become quality advocates, risk assessors, domain experts, and collaboration facilitators-contributing value throughout the development lifecycle rather than just at the end. From the earliest planning stages, testers help identify potential issues and testing challenges. During release planning, they ask questions about how features will be tested, what environments will be needed, and what risks might affect delivery. These questions often reveal hidden complexities that affect estimation and prioritization. When stories are being defined, testers help create concrete examples that clarify requirements. They think beyond the happy path to consider edge cases, error conditions, and user experience concerns. This prevents the "that's not what I meant" moments that plague traditional development. During development iterations, testers work closely with developers-writing tests that guide implementation, providing quick feedback on emerging functionality, and helping troubleshoot issues. Rather than working sequentially (developers code, then testers test), they work in parallel, with testing activities happening alongside development. Testers also serve as a bridge between technical and business perspectives. They translate between developer language and customer language, ensuring that technical decisions align with business goals. When misunderstandings occur, testers often facilitate resolution through techniques like the "Power of Three"-bringing together a developer, a customer representative, and a tester to clarify requirements. Perhaps most importantly, testers bring a unique perspective that complements the developer mindset. While developers naturally focus on making things work, testers consider how things might fail. They ask "what if" questions that others might miss: What if the user enters invalid data? What if the network connection is slow? What if the database is corrupted? This role requires a broad skill set. Modern agile testers need technical skills to work with automation tools, domain knowledge to understand business requirements, communication skills to collaborate effectively, and analytical skills to evaluate risks and prioritize testing efforts. The transition to this role can be challenging for testers accustomed to traditional environments. Instead of comprehensive test plans and detailed documentation, they must become comfortable with lightweight planning and just-enough documentation. Instead of receiving completed features to test, they must engage throughout the development process. And instead of being the sole guardians of quality, they must share that responsibility with the entire team.

Capítulo 8

Testing Throughout the Agile Lifecycle

Agile testing isn't confined to a specific phase-it happens continuously throughout the development lifecycle. Understanding how testing activities flow through release planning, iteration planning, development, and delivery helps teams integrate testing effectively into their process. During release planning, testers help size and prioritize stories by identifying testing challenges and potential ripple effects. They consider what test environments, data, and tools will be needed. They may create lightweight test plans or matrices to visualize testing coverage across the system. This early involvement ensures that testing needs are considered in the overall project plan. As iterations begin, testers collaborate with customers and developers to define acceptance criteria and create high-level tests. They help transform examples into executable tests that will guide development. They ensure stories are testable and that the team understands what "done" means from a testing perspective. During development, testing and coding progress hand-in-hand. Testers write detailed tests that drive implementation, starting with simple "happy path" scenarios and adding complexity as development progresses. They perform exploratory testing on emerging functionality, providing immediate feedback to developers. They collaborate closely with programmers through practices like pair testing, where a developer and tester evaluate new functionality together. When bugs are found, testers don't just report them-they work with developers to understand and fix them immediately. Many teams practice "zero bug tolerance," fixing issues as soon as they're discovered rather than accumulating a backlog of defects. As iterations conclude, testers help prepare demonstrations for stakeholders, gathering feedback that informs future iterations. They participate in retrospectives, identifying ways to improve the testing process. They ensure that automated tests from the current iteration are integrated into the regression suite for continuous testing. Before releases, testers focus on "end game" activities-final exploratory testing, integration with external systems, data migration verification, and installation testing. They coordinate user acceptance testing and help address any last-minute issues that arise. Throughout this cycle, testers maintain a dual focus-ensuring current stories meet requirements while considering how they fit into the larger system. They balance automated testing (which provides a safety net for regression) with manual exploratory testing (which uncovers issues automated tests might miss). This continuous testing approach requires flexibility and collaboration. Rather than following rigid test plans, testers adapt their activities based on the team's needs and the specific challenges of each story. They work closely with both the development team and customer representatives, facilitating communication and ensuring quality remains a shared priority.

Saca más partido a Pruebas ágiles

Recibe ideas a diario de más de 100 mil lecciones
Las palabras se iluminan al ritmo del audio
Tu biblioteca guardada en todos tus dispositivos

Capítulo 9

Overcoming Common Challenges

Implementing agile testing isn't without challenges. Teams often encounter obstacles related to organizational culture, technical infrastructure, and the testing mindset itself. Understanding these challenges-and strategies to overcome them-can help teams successfully transition to agile testing. One common challenge is resistance to the whole-team approach. Developers may resist taking responsibility for testing, while testers may fear losing their specialized role. Organizations may maintain separate testing departments, creating artificial barriers to collaboration. Overcoming this requires education about the benefits of shared responsibility, gradual cultural change, and leadership that models collaborative behavior. Technical debt presents another significant challenge. Many teams inherit legacy systems with little or no automated testing, making it difficult to implement agile practices. The solution involves a strategic approach: gradually building automated tests around the most critical or frequently changing parts of the system, using techniques like the "strangler pattern" to replace legacy code incrementally, and allocating time in each iteration to reduce technical debt. Test automation itself poses challenges, particularly for teams new to agile. Many struggle with the "hump of pain"-the initial investment required to build automation infrastructure and skills. Success requires management support for this investment, a focus on long-term benefits rather than short-term costs, and a pragmatic approach that starts with the most valuable automation opportunities. Distributed teams face unique challenges in implementing agile testing. When team members work across different locations or time zones, the close collaboration essential to agile testing becomes more difficult. Teams can mitigate this through regular video conferences, collaborative tools, shared documentation, and occasional in-person meetings to build relationships. Organizational policies and compliance requirements sometimes conflict with agile principles. For example, regulated industries may require extensive documentation or formal sign-offs that seem at odds with agile's flexibility. The key is finding creative ways to meet these requirements within an agile framework-such as generating documentation from automated tests or incorporating compliance checks into the definition of "done." Perhaps the most fundamental challenge is shifting the testing mindset from verification to prevention. Many testers are accustomed to finding bugs after development rather than preventing them through early involvement. This transition requires patience, mentoring, and concrete examples of how early testing activities contribute to quality. Teams that successfully overcome these challenges don't just implement agile testing practices-they adapt them to their specific context. They recognize that agile isn't a one-size-fits-all methodology but a set of principles that can be applied in various ways depending on the team's needs, the product's requirements, and the organization's constraints.

Capítulo 10

The Future of Agile Testing

As technology evolves and agile practices mature, the field of agile testing continues to develop. Several trends are shaping its future, creating both new challenges and opportunities for quality professionals. DevOps and continuous delivery are extending agile principles beyond development to operations, requiring even faster feedback cycles and more sophisticated automation. Testers are increasingly involved in monitoring production systems, analyzing real user data, and participating in operational decisions. The boundary between testing environments and production is becoming more fluid, with techniques like feature toggles and canary releases enabling safer production testing. Artificial intelligence and machine learning are transforming testing tools, enabling more intelligent test generation, execution, and analysis. These technologies can help identify patterns in test results, predict which areas of code are most likely to contain defects, and even generate test cases based on user behavior. While AI won't replace human testers, it will augment their capabilities and allow them to focus on more creative and strategic aspects of testing. The rise of microservices architectures presents new testing challenges, as systems become more distributed and complex. Testers need to understand concepts like service virtualization, contract testing, and chaos engineering to effectively test these architectures. The traditional testing pyramid is evolving to address these challenges, with greater emphasis on API testing and service integration. Security testing is becoming more integrated with agile processes as organizations recognize that security can't be an afterthought. The concept of "DevSecOps" emphasizes security throughout the development lifecycle, with testers playing a key role in identifying security risks and ensuring appropriate controls are in place. As user experiences become more complex-spanning multiple devices, channels, and contexts-testing must evolve to address this complexity. Testers need to consider accessibility, internationalization, and cross-platform compatibility from the earliest stages of development. They must also develop skills in testing emerging technologies like augmented reality, voice interfaces, and Internet of Things devices. The role of the tester continues to evolve as well. While specialized testing skills remain valuable, the boundaries between development, testing, and operations are becoming less distinct. Many testers are developing programming skills to contribute more effectively to automation efforts, while developers are learning testing techniques to improve their code quality. This doesn't mean the testing role will disappear-rather, it will transform into a quality coaching role that helps the entire team deliver better software. Throughout these changes, the fundamental principles of agile testing remain relevant: collaboration over silos, prevention over detection, and customer value over comprehensive documentation. By embracing these principles while adapting to new technologies and methodologies, agile testers will continue to play a vital role in delivering high-quality software that meets user needs.

Ve cada palabra mientras la escuchas

Sigue la lectura sin esfuerzo mientras cada palabra de Pruebas ágiles se ilumina en tiempo real.

Capítulo 11

Conclusion: Quality is a Journey, Not a Destination

"Agile Testing" presents a vision of quality as an ongoing journey rather than a final checkpoint. This perspective fundamentally transforms how teams approach software development, moving from a "build then test" mentality to one where quality is built in from the beginning through collaboration, automation, and continuous feedback. The book's most powerful message is that quality isn't achieved through rigid processes or comprehensive documentation, but through people working together effectively. It's about creating an environment where everyone cares about quality and has the skills, tools, and mindset to contribute to it. This journey isn't always easy. Teams face technical challenges in implementing test automation, cultural challenges in adopting the whole-team approach, and organizational challenges in securing the time and resources needed for quality work. But those who persist discover that agile testing not only improves product quality but also makes the development process more enjoyable and sustainable. As we navigate an increasingly complex technological landscape, the principles outlined by Crispin and Gregory become even more relevant. The pace of change continues to accelerate, making traditional testing approaches increasingly inadequate. Agile testing-with its emphasis on adaptation, collaboration, and continuous learning-provides a framework that can evolve with these changes. The journey toward better quality never truly ends. There are always new testing techniques to explore, new tools to master, and new challenges to overcome. But by embracing the agile testing mindset and practices, teams can create products that not only meet specifications but truly delight users-and that's the ultimate measure of quality.

★★★★★

Has llegado al final de Pruebas ágiles

Más de 1 millón de estudiantes lo adoran

“Llevo 23 días y lo he usado todos los días. Ya forma parte de mi rutina diaria.”

jayallen

Temas clave en Pruebas ágiles

whole-team quality
continuous testing
agile testing quadrants
defect prevention
collaborative software development

Citas de Pruebas ágiles

Testing is not a phase.
Quality can't be 'tested in' at the end of development.
Quality becomes everyone's responsibility-not just designated testers.
How can I help the team deliver what the customer really needs?

Personajes en Pruebas ágiles

Lisa CrispinCo-author and expert in agile testing
Janet GregoryCo-author and agile testing specialist
Brian MarickCreator of the original Agile Testing Quadrants

Sobre el Autor

Lisa Crispin es coautora de Agile Testing: A Practical Guide for Testers and Agile Teams y una autoridad líder en metodologías de pruebas de software ágiles.

Pionera en prácticas de pruebas colaborativas, ha definido los estándares de la industria a través de obras como More Agile Testing: Learning Journeys for the Whole Team y Agile Testing Condensed, escritos en coautoría con Janet Gregory. Sus libros enfatizan el enfoque de "todo el equipo" hacia la calidad, combinando el rigor técnico con estrategias prácticas para integrar las pruebas en los flujos de trabajo ágiles y DevOps.

Crispin cofundó el Agile Testing Fellowship, que ofrece programas de capacitación reconocidos mundialmente sobre pruebas holísticas y entrega continua. Elegida como la Profesional de Pruebas Ágiles Más Influyente en 2012, sus conocimientos se basan en décadas de experiencia práctica con equipos de alto rendimiento y en la promoción de las pruebas exploratorias.

Ponente frecuente en conferencias como Agile Testing Days, el trabajo de Crispin sigue siendo una piedra angular para los profesionales del software, elogiado por sus marcos de trabajo accionables y su relevancia duradera en los entornos de desarrollo en constante evolución.

Descargar resumen de Pruebas ágiles

Obtén el resumen de Pruebas ágiles como PDF o EPUB gratis. Imprímelo o léelo sin conexión en cualquier momento.

A los usuarios también les gustó

Learning Agile

Andrew Stellman & Jennifer Greene

Portada del libro The Testing Revolution: Beyond 'Just Testing'

Software Testing Methodologies Guide: A High-Level Overview

10 Best QA Testing Tools of 2025 - GeeksforGeeks

6 sources

The Testing Revolution: Beyond 'Just Testing'

Portada del libro Transforming Software Testing: From Checkpoint to Collaboration

System Design Interview – An Insider's Guide

A Philosophy of Software Design, 2nd Edition

6 sources

Transforming Software Testing: From Checkpoint to Collaboration

Portada del libro Testing Strategies That Actually Work

21 sources

Testing Strategies That Actually Work

Portada del libro Testing: The Crucible of Life

6 sources

Testing: The Crucible of Life

Portada del libro From Fire to Code: Testing's Strategic Evolution

23 sources

From Fire to Code: Testing's Strategic Evolution

The elements of scrum

Chris Sims& Hillary Louise Johnson

Portada del libro The Art of Testing: From Exams to Automation

28 sources

The Art of Testing: From Exams to Automation

Preguntas Frecuentes Sobre Este Libro

Parte de un plan de aprendizaje

PLAN DE APRENDIZAJE

Build Cross-Platform Library for Mobile & Web

5 h 46 m•4 Episodios

Descubre más

PLAN DE APRENDIZAJE

Python Testing Learning Plan

Testing is essential for building reliable, maintainable software that scales with your projects and team. This learning plan is ideal for Python developers who want to level up their code quality, software engineers transitioning to test-driven workflows, and teams looking to implement robust testing practices and automation in their development process.

2 h 8 m•4 Secciones

PLAN DE APRENDIZAJE

Master Agile Scrum for Small Business

This plan is essential for small business owners and team leads looking to increase efficiency without the overhead of enterprise-level systems. It provides a roadmap for transitioning from chaotic workflows to structured, high-performing Agile environments.

4 h 4 m•4 Secciones

PLAN DE APRENDIZAJE

Observability and Testing in Go and Rust

System reliability depends on the synergy between deep observability and rigorous testing. This plan is ideal for backend engineers working in Go and Rust who need to bridge the gap between development and production stability.

1 h 30 m•3 Secciones

PLAN DE APRENDIZAJE

Automated Quality Governance for Product Owners

In an era of AI-driven development, traditional manual oversight is no longer sufficient to ensure product quality. This plan is designed for Product Owners who need to automate governance and align technical health metrics with strategic business outcomes.

1 h 30 m•3 Secciones

PLAN DE APRENDIZAJE

The Diagnostic for Tool Enshittification

As software platforms increasingly prioritize monetization over utility, developers must learn to identify predatory technical patterns. This guide is essential for software architects and engineers who want to build resilient stacks and avoid becoming locked into decaying ecosystems.

1 h 30 m•3 Secciones

PLAN DE APRENDIZAJE

Claude Code: Zero to Agentic Builder

This plan is essential for developers looking to move beyond simple chat interfaces into autonomous AI engineering. It benefits software engineers and tech leads who want to leverage agentic workflows to automate repetitive coding tasks and system integrations.

1 h 12 m•3 Secciones

PLAN DE APRENDIZAJE

Learn software dev

This comprehensive learning path takes you from programming beginner to professional software engineer, covering everything from writing your first line of code to making architectural decisions for large-scale systems. It's ideal for career changers entering tech, self-taught programmers looking to formalize their skills, or junior developers aiming to reach senior-level expertise. The structured progression ensures you build both technical proficiency and the professional mindset needed to succeed in modern software development teams.

4 h 50 m•4 Secciones

PLAN DE APRENDIZAJE

read mom test

The Mom Test methodology helps entrepreneurs and product builders avoid the common pitfall of receiving false validation for their ideas. This learning plan teaches practical skills for conducting effective customer interviews that reveal genuine needs and problems, essential for anyone developing products or services who wants to minimize risk and maximize market fit.

3 h 33 m•4 Secciones

Creado por exalumnos de la Universidad de Columbia en San Francisco

LOVED BY

1,000,000+ curious minds.

4.7

avg rating

1M+ learners

"Instead of endless scrolling, I just hit play on BeFreed. It saves me so much time."

@Moemenn

"I never knew where to start with nonfiction—BeFreed’s book lists turned into podcasts gave me a clear path."

@Chloe, Solo founder, LA

117

"Perfect balance between learning and entertainment. Finished ‘Thinking, Fast and Slow’ on my commute this week."

@Raaaaaachelw

"Crazy how much I learned while walking the dog. BeFreed = small habits → big gains."

@Matt, YC alum

108

"Reading used to feel like a chore. Now it’s just part of my lifestyle."

@Erin, Investment Banking Associate , NYC

254

"Feels effortless compared to reading. I’ve finished 6 books this month already."

@djmikemoore

"BeFreed turned my guilty doomscrolling into something that feels productive and inspiring."

@Pitiful

4.5K

"BeFreed turned my commute into learning time. 20-min podcasts are perfect for finishing books I never had time for."

@SofiaP

"BeFreed replaced my podcast queue. Imagine Spotify for books — that’s it. 🙌"

@Jaded_Falcon

201

"It is great for me to learn something from the book without reading it."

@OojasSalunke

"The themed book list podcasts help me connect ideas across authors—like a guided audio journey."

@Leo, Law Student, UPenn

483

"Makes me feel smarter every time before going to work"

@Cashflowbubu

Ver más sobre cómo se habla de BeFreed en la web

Creado por exalumnos de la Universidad de Columbia en San Francisco

LOVED BY

1,000,000+ curious minds.

4.7

avg rating

1M+ learners

"Instead of endless scrolling, I just hit play on BeFreed. It saves me so much time."

@Moemenn

"I never knew where to start with nonfiction—BeFreed’s book lists turned into podcasts gave me a clear path."

@Chloe, Solo founder, LA

117

"Perfect balance between learning and entertainment. Finished ‘Thinking, Fast and Slow’ on my commute this week."

@Raaaaaachelw

"Crazy how much I learned while walking the dog. BeFreed = small habits → big gains."

@Matt, YC alum

108

"Reading used to feel like a chore. Now it’s just part of my lifestyle."

@Erin, Investment Banking Associate , NYC

254

"Feels effortless compared to reading. I’ve finished 6 books this month already."

@djmikemoore

"BeFreed turned my guilty doomscrolling into something that feels productive and inspiring."

@Pitiful

4.5K

"BeFreed turned my commute into learning time. 20-min podcasts are perfect for finishing books I never had time for."

@SofiaP

"BeFreed replaced my podcast queue. Imagine Spotify for books — that’s it. 🙌"

@Jaded_Falcon

201

"It is great for me to learn something from the book without reading it."

@OojasSalunke

"The themed book list podcasts help me connect ideas across authors—like a guided audio journey."

@Leo, Law Student, UPenn

483

"Makes me feel smarter every time before going to work"

@Cashflowbubu

"Instead of endless scrolling, I just hit play on BeFreed. It saves me so much time."

@Moemenn

"I never knew where to start with nonfiction—BeFreed’s book lists turned into podcasts gave me a clear path."

@Chloe, Solo founder, LA

117

"Perfect balance between learning and entertainment. Finished ‘Thinking, Fast and Slow’ on my commute this week."

@Raaaaaachelw

"Crazy how much I learned while walking the dog. BeFreed = small habits → big gains."

@Matt, YC alum

108

"Reading used to feel like a chore. Now it’s just part of my lifestyle."

@Erin, Investment Banking Associate , NYC

254

"Feels effortless compared to reading. I’ve finished 6 books this month already."

@djmikemoore

"BeFreed turned my guilty doomscrolling into something that feels productive and inspiring."

@Pitiful

4.5K

"BeFreed turned my commute into learning time. 20-min podcasts are perfect for finishing books I never had time for."

@SofiaP

"BeFreed replaced my podcast queue. Imagine Spotify for books — that’s it. 🙌"

@Jaded_Falcon

201

"It is great for me to learn something from the book without reading it."

@OojasSalunke

"The themed book list podcasts help me connect ideas across authors—like a guided audio journey."

@Leo, Law Student, UPenn

483

"Makes me feel smarter every time before going to work"

@Cashflowbubu

"Instead of endless scrolling, I just hit play on BeFreed. It saves me so much time."

@Moemenn

"I never knew where to start with nonfiction—BeFreed’s book lists turned into podcasts gave me a clear path."

@Chloe, Solo founder, LA

117

"Perfect balance between learning and entertainment. Finished ‘Thinking, Fast and Slow’ on my commute this week."

@Raaaaaachelw

"Crazy how much I learned while walking the dog. BeFreed = small habits → big gains."

@Matt, YC alum

108

"Reading used to feel like a chore. Now it’s just part of my lifestyle."

@Erin, Investment Banking Associate , NYC

254

"Feels effortless compared to reading. I’ve finished 6 books this month already."

@djmikemoore

"BeFreed turned my guilty doomscrolling into something that feels productive and inspiring."

@Pitiful

4.5K

"BeFreed turned my commute into learning time. 20-min podcasts are perfect for finishing books I never had time for."

@SofiaP

"BeFreed replaced my podcast queue. Imagine Spotify for books — that’s it. 🙌"

@Jaded_Falcon

201

"It is great for me to learn something from the book without reading it."

@OojasSalunke

"The themed book list podcasts help me connect ideas across authors—like a guided audio journey."

@Leo, Law Student, UPenn

483

"Makes me feel smarter every time before going to work"

@Cashflowbubu

Ver más sobre cómo se habla de BeFreed en la web

Comienza tu viaje de aprendizaje, ahora

Capítulo 10

Pruebas ágiles

ResumenResumen de Pruebas ágiles

Un libro. Muchas formas de escucharlo.

Transforming Quality: The Revolution of Agile Testing

The Whole-Team Approach to Quality

Ve cada palabra mientras la escuchas

The Agile Testing Mindset

The Four Quadrants of Agile Testing

Saca más partido a Pruebas ágiles

Driving Development with Tests

The Automation Pyramid

Ve cada palabra mientras la escuchas

The Tester's Role in Agile Teams

Testing Throughout the Agile Lifecycle

Saca más partido a Pruebas ágiles

Overcoming Common Challenges

The Future of Agile Testing

Ve cada palabra mientras la escuchas

Conclusion: Quality is a Journey, Not a Destination

Has llegado al final de Pruebas ágiles

Temas clave en Pruebas ágiles

Citas de Pruebas ágiles

Personajes en Pruebas ágiles

Sobre el Autor

Descargar resumen de Pruebas ágiles

A los usuarios también les gustó

Preguntas Frecuentes Sobre Este Libro

What is Agile Testing: A Practical Guide for Testers and Agile Teams about?

Who should read Agile Testing: A Practical Guide for Testers and Agile Teams?

Is Agile Testing by Lisa Crispin worth reading?

What is the Agile Testing Matrix in Agile Testing?

Parte de un plan de aprendizaje

Build Cross-Platform Library for Mobile & Web

Descubre más

1,000,000+ curious minds.

1,000,000+ curious minds.

Un libro. Muchas formas de escucharlo.

Transforming Quality: The Revolution of Agile Testing

The Whole-Team Approach to Quality

Ve cada palabra mientras la escuchas

The Agile Testing Mindset

The Four Quadrants of Agile Testing

Saca más partido a Pruebas ágiles

Driving Development with Tests

The Automation Pyramid

Ve cada palabra mientras la escuchas

The Tester's Role in Agile Teams

Testing Throughout the Agile Lifecycle

Saca más partido a Pruebas ágiles

Overcoming Common Challenges

The Future of Agile Testing

Ve cada palabra mientras la escuchas

Conclusion: Quality is a Journey, Not a Destination

Has llegado al final de Pruebas ágiles

A los usuarios también les gustó

Parte de un plan de aprendizaje

Build Cross-Platform Library for Mobile & Web

Descubre más

Resumen de Pruebas ágiles