1

Step 1

Chapter 1 What Is Agile Testing, Anyway?

2

Step 2

Chapter 2 Ten Principles for Agile Testers

3

Step 3

Chapter 3 Cultural Challenges

4

Step 4

Chapter 4 Team Logistics

5

Step 5

Chapter 5 Transitioning Typical Processes

6

Step 6

Chapter 6 The Purpose of Testing

7

Step 7

Chapter 7 Technology-Facing Tests that Support the Team

8

Step 8

Chapter 8 Business-Facing Tests that Support the Team

9

Step 9

Chapter 9 Toolkit for Business-Facing Tests that Support the Team

10

Step 10

Chapter 10 Business-Facing Tests that Critique the Product

11

Step 11

Chapter 11 Critiquing the Product Using Technology-Facing Tests

12

Step 12

Chapter 12 Summary of Testing Quadrants

13

Step 13

Chapter 13 Why We Want to Automate Tests and What Holds Us Back

14

Step 14

Chapter 14 An Agile Test Automation Strategy

15

Step 15

Chapter 15 Tester Activities in Release or Theme Planning

16

Step 16

Chapter 16 Hit the Ground Running

17

Step 17

Chapter 17 Iteration Kickoff

18

Step 18

Chapter 18 Coding and Testing

19

Step 19

Chapter 19 Wrap Up the Iteration

20

Step 20

Chapter 20 Successful Delivery

21

Step 21

Chapter 21 Key Success Factors

1

Step 1

Chapter 1 What Is Agile Testing, Anyway?

2

Step 2

Chapter 2 Ten Principles for Agile Testers

3

Step 3

Chapter 3 Cultural Challenges

4

Step 4

Chapter 4 Team Logistics

5

Step 5

Chapter 5 Transitioning Typical Processes

6

Step 6

Chapter 6 The Purpose of Testing

7

Step 7

Chapter 7 Technology-Facing Tests that Support the Team

8

Step 8

Chapter 8 Business-Facing Tests that Support the Team

9

Step 9

Chapter 9 Toolkit for Business-Facing Tests that Support the Team

10

Step 10

Chapter 10 Business-Facing Tests that Critique the Product

11

Step 11

Chapter 11 Critiquing the Product Using Technology-Facing Tests

12

Step 12

Chapter 12 Summary of Testing Quadrants

13

Step 13

Chapter 13 Why We Want to Automate Tests and What Holds Us Back

14

Step 14

Chapter 14 An Agile Test Automation Strategy

15

Step 15

Chapter 15 Tester Activities in Release or Theme Planning

16

Step 16

Chapter 16 Hit the Ground Running

17

Step 17

Chapter 17 Iteration Kickoff

18

Step 18

Chapter 18 Coding and Testing

19

Step 19

Chapter 19 Wrap Up the Iteration

20

Step 20

Chapter 20 Successful Delivery

21

Step 21

Chapter 21 Key Success Factors

02 January 2021
completed_date

Goal author

silva05

Russia, Санкт-Петербург

Education

Lisa Crispin - Agile Testing

Прочитать и законспектировать

  1. Chapter 1 What Is Agile Testing, Anyway?

    1. Agile Values

    2. What Do We Mean by “Agile Testing”?

    3. A Little Context for Roles and Activities on an Agile Team

    4. Customer Team

    5. Developer Team

    6. Interaction between Customer and Developer Teams

    7. How Is Agile Testing Different?

    8. Working on Traditional Teams

    9. Working on Agile Teams

    10. Traditional vs. Agile Testing

    11. Whole-Team Approach

    12. Summary

  2. Chapter 2 Ten Principles for Agile Testers

    1. What’s an Agile Tester?

    2. The Agile Testing Mind-Set

    3. Applying Agile Principles and Values

    4. Provide Continuous Feedback

    5. Deliver Value to the Customer

    6. Enable Face-to-Face Communication

    7. Have Courage

    8. Keep It Simple

    9. Practice Continuous Improvement

    10. Respond to Change

    11. Self-Organize

    12. Focus on People

    13. Enjoy

    14. Adding Value

    15. Summary

  3. Chapter 3 Cultural Challenges

    1. Organizational Culture

    2. Quality Philosophy

    3. Sustainable Pace

    4. Customer Relationships

    5. Organization Size

    6. Empower Your Team

    7. Barriers to Successful Agile Adoption by Test/QA Teams

    8. Loss of Identity

    9. Additional Roles

    10. Lack of Training

    11. Not Understanding Agile Concepts

    12. Past Experience/Attitude

    13. Cultural Differences among Roles

    14. Introducing Change

    15. Talk about Fears

    16. Give Team Ownership

    17. Celebrate Success

    18. Management Expectations

    19. Cultural Changes for Managers

    20. Speaking the Manager’s Language

    21. Change Doesn’t Come Easy

    22. Be Patient

    23. Let Them Feel Pain

    24. Build Your Credibility

    25. Work On Your Own Professional Development

    26. Beware the Quality Police Mentality

    27. Vote with Your Feet

    28. Summary

  4. Chapter 4 Team Logistics

    1. Team Structure

    2. Independent QA Teams

    3. Integration of Testers into an Agile Project

    4. Agile Project Teams

    5. Physical Logistics

    6. Resources

    7. Tester-Developer Ratio

    8. Hiring an Agile Tester

    9. Building a Team

    10. Self-Organizing Team

    11. Involving Other Teams

    12. Every Team Member Has Equal Value

    13. Performance and Rewards

    14. What Can You Do?

    15. Summary

  5. Chapter 5 Transitioning Typical Processes

    1. Seeking Lightweight Processes

    2. Metrics

    3. Lean Measurements

    4. Why We Need Metrics

    5. What Not to Do with Metrics

    6. Communicating Metrics

    7. Metrics ROI

    8. Defect Tracking

    9. Why Should We Use a Defect Tracking System (DTS)?

    10. Why Shouldn’t We Use a DTS?

    11. Defect Tracking Tools

    12. Keep Your Focus

    13. Test Planning

    14. Test Strategy vs. Test Planning

    15. Traceability

    16. Existing Processes and Models

    17. Audits

    18. Frameworks, Models, and Standards

    19. Summary

  6. Chapter 6 The Purpose of Testing

    1. The Agile Testing Quadrants

    2. Tests that Support the Team

    3. Tests that Critique the Product

    4. Knowing When a Story Is Done

    5. Shared Responsibility

    6. Managing Technical Debt

    7. Testing in Context

    8. Summary

  7. Chapter 7 Technology-Facing Tests that Support the Team

    1. An Agile Testing Foundation

    2. The Purpose of Quadrant 1 Tests

    3. Supporting Infrastructure

    4. Why Write and Execute These Tests?

    5. Lets Us Go Faster and Do More

    6. Making Testers’ Jobs Easier

    7. Designing with Testing in Mind

    8. Timely Feedback

    9. Where Do Technology-Facing Tests Stop?

    10. What If the Team Doesn’t Do These Tests?

    11. What Can Testers Do?

    12. What Can Managers Do?

    13. It’s a Team Problem

    14. Toolkit

    15. Source Code Control

    16. IDEs

    17. Build Tools

    18. Build Automation Tools

    19. Unit Test Tools

    20. Summary

  8. Chapter 8 Business-Facing Tests that Support the Team

    1. Driving Development with Business-Facing Tests

    2. The Requirements Quandary

    3. Common Language

    4. Eliciting Requirements

    5. Advance Clarity

    6. Conditions of Satisfaction

    7. Ripple Effects

    8. Thin Slices, Small Chunks

    9. How Do We Know We’re Done?

    10. Tests Mitigate Risk

    11. Testability and Automation

    12. Summary

  9. Chapter 9 Toolkit for Business-Facing Tests that Support the Team

    1. Business-Facing Test Tool Strategy

    2. Tools to Elicit Examples and Requirements

    3. Checklists

    4. Mind Maps

    5. Spreadsheets

    6. Mock-Ups

    7. Flow Diagrams

    8. Software-Based Tools

    9. Tools for Automating Tests Based on Examples

    10. Tools to Test below the GUI and API Level

    11. Tools for Testing through the GUI

    12. Strategies for Writing Tests

    13. Build Tests Incrementally

    14. Keep the Tests Passing

    15. Use Appropriate Test Design Patterns

    16. Keyword and Data-Driven Tests

    17. Testability

    18. Code Design and Test Design

    19. Automated vs. Manual Quadrant 2 Tests

    20. Test Management

    21. Summary

  10. Chapter 10 Business-Facing Tests that Critique the Product

    1. Introduction to Quadrant 3

    2. Demonstrations

    3. Scenario Testing

    4. Exploratory Testing

    5. Session-Based Testing

    6. Automation and Exploratory Testing

    7. An Exploratory Tester

    8. Usability Testing

    9. User Needs and Persona Testing

    10. Navigation

    11. Check Out the Competition

    12. Behind the GUI

    13. API Testing

    14. Web Services

    15. Testing Documents and Documentation

    16. User Documentation

    17. Reports

    18. Tools to Assist with Exploratory Testing

    19. Test Setup

    20. Test Data Generation

    21. Monitoring Tools

    22. Simulators

    23. Emulators

    24. Summary

  11. Chapter 11 Critiquing the Product Using Technology-Facing Tests

    1. Introduction to Quadrant 4

    2. Who Does It?

    3. When Do You Do It?

    4. “ility” Testing

    5. Security

    6. Maintainability

    7. Interoperability

    8. Compatibility

    9. Reliability

    10. Installability

    11. “ility” Summary

    12. Performance, Load, Stress, and Scalability Testing

    13. Scalability

    14. Performance and Load Testing

    15. Performance and Load-Testing Tools

    16. Baseline

    17. Test Environments

    18. Memory Management

    19. Summary

  12. Chapter 12 Summary of Testing Quadrants

    1. Review of the Testing Quadrants

    2. A System Test Example

    3. The Application

    4. The Team and the Process

    5. Tests Driving Development

    6. Unit Tests

    7. Acceptance Tests

    8. Automation

    9. The Automated Functional Test Structure

    10. Web Services

    11. Embedded Testing

    12. Critiquing the Product with Business-Facing Tests

    13. Exploratory Testing

    14. Testing Data Feeds

    15. The End-to-End Tests

    16. User Acceptance Testing

    17. Reliability

    18. Documentation

    19. Documenting the Test Code

    20. Reporting the Test Results

    21. Using the Agile Testing Quadrants

    22. Summary

  13. Chapter 13 Why We Want to Automate Tests and What Holds Us Back

    1. Why Automate?

    2. Manual Testing Takes Too Long

    3. Manual Processes Are Error Prone

    4. Automation Frees People to Do Their Best Work

    5. Automated Regression Tests Provide a Safety Net

    6. Automated Tests Give Feedback, Early and Often

    7. Tests and Examples that Drive Coding Can Do More

    8. Tests Are Great Documentation

    9. ROI and Payback

    10. Barriers to Automation—Things that Get in the Way

    11. Bret’s List

    12. Our List

    13. Programmers’ Attitude—“Why Automate?”

    14. The “Hump of Pain” (The Learning Curve)

    15. Initial Investment

    16. Code that’s Always in Flux

    17. Legacy Code

    18. Fear

    19. Old Habits

    20. Can We Overcome These Barriers?

    21. Summary

  14. Chapter 14 An Agile Test Automation Strategy

    1. An Agile Approach to Test Automation

    2. Automation Test Categories

    3. Test Automation Pyramid

    4. What Can We Automate?

    5. Continuous Integration, Builds, and Deploys

    6. Unit and Component Tests

    7. API or Web Services Testing

    8. Testing behind the GUI

    9. Testing the GUI

    10. Load Tests

    11. Comparisons

    12. Repetitive Tasks

    13. Data Creation or Setup

    14. What Shouldn’t We Automate?

    15. Usability Testing

    16. Exploratory Testing

    17. Tests that Will Never Fail

    18. One-Off Tests

    19. What Might Be Hard to Automate?

    20. Developing an Automation Strategy—Where Do We Start?

    21. Where Does It Hurt the Most?

    22. Multi-Layered Approach

    23. Think about Test Design and Maintenance

    24. Choosing the Right Tools

    25. Applying Agile Principles to Test Automation

    26. Keep It Simple

    27. Iterative Feedback

    28. Whole-Team Approach

    29. Taking the Time to Do It Right

    30. Learn by Doing

    31. Apply Agile Coding Practices to Tests

    32. Supplying Data for Tests

    33. Data Generation Tools

    34. Avoid Database Access

    35. When Database Access Is Unavoidable or Even Desirable

    36. Understand Your Needs

    37. Evaluating Automation Tools

    38. Identifying Requirements for Your Automation Tool

    39. One Tool at a Time

    40. Choosing Tools

    41. Agile-Friendly Tools

    42. Implementing Automation

    43. Managing Automated Tests

    44. Organizing Tests

    45. Organizing Test Results

    46. Go Get Started

    47. Summary

  15. Chapter 15 Tester Activities in Release or Theme Planning

    1. The Purpose of Release Planning

    2. Sizing

    3. How to Size Stories

    4. The Tester’s Role in Sizing Stories

    5. An Example of Sizing Stories

    6. Prioritizing

    7. Why We Prioritize Stories

    8. Testing Considerations While Prioritizing

    9. What’s in Scope?

    10. Deadlines and Timelines

    11. Focus on Value

    12. System-Wide Impact

    13. Third-Party Involvement

    14. Test Planning

    15. Where to Start

    16. Why Write a Test Plan?

    17. Types of Testing

    18. Infrastructure

    19. Test Environments

    20. Test Data

    21. Test Results

    22. Test Plan Alternatives

    23. Lightweight Test Plans

    24. Using a Test Matrix

    25. Test Spreadsheet

    26. A Whiteboard

    27. Automated Test List

    28. Preparing for Visibility

    29. Tracking Test Tasks and Status

    30. Communicating Test Results

    31. Release Metrics

    32. Summary

  16. Chapter 16 Hit the Ground Running

    1. Be Proactive

    2. Benefits

    3. Do You Really Need This?

    4. Potential Downsides to Advance Preparation

    5. Advance Clarity

    6. Customers Speak with One Voice

    7. Story Size

    8. Geographically Dispersed Teams

    9. Examples

    10. Test Strategies

    11. Prioritize Defects

    12. Resources

    13. Summary

  17. Chapter 17 Iteration Kickoff

    1. Iteration Planning

    2. Learning the Details

    3. Considering All Viewpoints

    4. Writing Task Cards

    5. Deciding on Workload

    6. Testable Stories

    7. Collaborate with Customers

    8. High-Level Tests and Examples

    9. Reviewing with Customers

    10. Reviewing with Programmers

    11. Test Cases as Documentation

    12. Summary

  18. Chapter 18 Coding and Testing

    1. Driving Development

    2. Start Simple

    3. Add Complexity

    4. Assess Risk

    5. Coding and Testing Progress Together

    6. Identify Variations

    7. Power of Three

    8. Focus on One Story

    9. Tests that Critique the Product

    10. Collaborate with Programmers

    11. Pair Testing

    12. “Show Me”

    13. Talk to Customers

    14. Show Customers

    15. Understand the Business

    16. Completing Testing Tasks

    17. Dealing with Bugs

    18. Is It a Defect or Is It a Feature?

    19. Technical Debt

    20. Zero Bug Tolerance

    21. It’s All about Choices

    22. Decide Which Bugs to Log

    23. Choose When to Fix Your Bugs

    24. Choose the Media You Should Use to Log a Bug

    25. Alternatives and Suggestions for Dealing with Bugs

    26. Start Simple

    27. Facilitate Communication

    28. Testers Facilitate Communication

    29. Distributed Teams

    30. Regression Tests

    31. Keep the Build “Green”

    32. Keep the Build Quick

    33. Building a Regression Suite

    34. Checking the “Big Picture”

    35. Resources

    36. Iteration Metrics

    37. Measuring Progress

    38. Defect Metrics

    39. Summary

  19. Chapter 19 Wrap Up the Iteration

    1. Iteration Demo

    2. Retrospectives

    3. Start, Stop, and Continue

    4. Ideas for Improvements

    5. Celebrate Successes

    6. Summary

  20. Chapter 20 Successful Delivery

    1. What Makes a Product?

    2. Planning Enough Time for Testing

    3. The End Game

    4. Testing the Release Candidate

    5. Test on a Staging Environment

    6. Final Nonfunctional Testing

    7. Integration with External Applications

    8. Data Conversion and Database Updates

    9. Installation Testing

    10. Communication

    11. What If It’s Not Ready?

    12. Customer Testing

    13. UAT

    14. Alpha/Beta Testing

    15. Post-Development Testing Cycles

    16. Deliverables

    17. Releasing the Product

    18. Release Acceptance Criteria

    19. Release Management

    20. Packaging

    21. Customer Expectations

    22. Production Support

    23. Understand Impact to Business

    24. Summary

  21. Chapter 21 Key Success Factors

    1. Success Factor 1: Use the Whole-Team Approach

    2. Success Factor 2: Adopt an Agile Testing Mind-Set

    3. Success Factor 3: Automate Regression Testing

    4. Success Factor 4: Provide and Obtain Feedback

    5. Success Factor 5: Build a Foundation of Core Practices

    6. Continuous Integration

    7. Test Environments

    8. Manage Technical Debt

    9. Working Incrementally

    10. Coding and Testing Are Part of One Process

    11. Synergy between Practices

    12. Success Factor 6: Collaborate with Customers

    13. Success Factor 7: Look at the Big Picture

    14. Summary

  • 701
  • 02 January 2021, 11:37
Sign up

Signup

Уже зарегистрированы?
Quick sign-up through social networks.
Sign in

Sign in.
Allowed.

Not registered yet?
 
Log in through social networks
Forgot your password?