Top 10 books Agile Tester should read

Tram Ho

1. Agile Testing

What does it mean to become an "aglie tester"? Does an agile team need a member with QA expertise? What is the real role of tester in Agile?

Testing is a key component in agile. The widespread adoption of agile also brought the need for an effective testing method ahead of the limelight, and agile projects also changed the original role of the tester. However, much of the tester's work is still misunderstood.

In Agile Testing, Crispin and Gregory give the definition of agile testing and describe the role of the tester from an example of an agile team in practice. The book teaches about

  • How to get the tester involved in agile
  • The position of the tester and the QA manager in an agile team
  • Requirement to recruit an agile tester
  • How does the tester change from a traditional model to an agile model?
  • How to complete testing in a short period
  • How to use testing to guide the development process
  • How to overcome barriers to automated testing

The Agile Testing book is a must-have book for an agile tester, team agile, manager and their customers. Book link: Agile Testing

2. User Stories Applied

The best way to build software that meets user needs is to start with "user stories": simple, clear, concise descriptions of the functionality that will be valuable to real users.

In User Stories Applied , you will learn what makes a great user story, and what makes a bad user story. You will discover practical ways to collect user stories, even if you can't talk to your users. Then, once you have compiled the user stories, the author tells us how to organize them, determine priorities and use them to plan, manage, and test. What will you learn in this book?

  • Model user roles: Understand what the user has in common and what is different
  • Collecting user stories: interviewing users, polling, observations and conferences
  • Work with managers, trainer, salespeople and other representatives
  • Write user stories for acceptance testing
  • Use user stories to set priorities, set schedules and estimate release costs
  • Includes practice questions at the end of the chapter and exercises

And more!

User Stories Applied is very useful for every developer, tester, analyst and manager with any agile method: XP, Scrum … or even your own approach.

Link: User Stories Applied

3. Specification by Example

The example specification is a collaborative method for defining requirements and testing.

In this book, author Gojko Adzic interviews successful teams around the world, sharing how they identify, develop and deliver the software, without error, during repeated short delivery cycles. again.

Case studies in this book include small startup websites for large financial institutions, operating in a variety of processes including XP, Scrum, and Kanban.

In Specification by Example, the author describes the concept of workable specifications that are automatically tested as documents. This type of document is always up to date, because it runs daily against the software to test it.

This book is for developers, testers and analysts working together to build the best software because it emphasizes the importance of understanding customer requirements and how to implement them. show it so it meets the needs of its customers.

Link: Specification by Example

4. Continuous Delivery

Releasing software for users is often a difficult, risky, and time-consuming process.

After reading this book, you will learn practical principles and techniques that enable users to provide quality, new features that are valuable and fast.

This book includes

  • Automate every aspect of software construction, integration, testing, and deployment
  • Implement deployment pipelines at team and organization level
  • Improve cooperation between deverloper, tester and operator
  • Develop added features on large and distributed stamps
  • Implementing an effective configuration management strategy
  • Automated acceptance testing, from analysis to execution
  • Testing capabilities and other non-functional requirements
  • Make ongoing deployments and ongoing releases
  • Infrastructure management, data, components and dependencies
  • Navigate risk management, compliance and auditing

Link: Continuous Delivery

5. Experiances of Test Automation

Test Automation has become a necessity for agile development. As applications and systems grow and become complex, manual testing cannot handle them all.

As technology changes, and there are more organizations moving to agile development, the test needs to adapt to it quickly. Test automation is essential, but unreasonable automation will cause waste – how do you know if the effort you spend is worth or not.

This book is about both management and technical issues, interpreting failures and successes, great ideas and bad decisions, and above all, giving you specific lessons. that you can use.


  • Test automation in agile development
  • How management support can create or destroy successful automation
  • The importance of a good test architecture and abstract levels
  • Measure benefits and returns from investment
  • Management issues, including skills, planning or, scope and contingencies
  • Model-Based Testing (MBT), monkey testing, and exploratory test automation
  • The importance of standards, communication, documentation, and flexibility in enterprise-wide automation
  • Activities that support automation
  • What test should automate, what test should not
  • Implicit costs for automation: maintenance and analysis fail
  • The exact goal of test automation: why "finding bugs" is not a good goal
  • Highlights, including received lessons, good points, and helpful tips
  • The Experiences of Test Automation will be valuable to those who are reviewing, implementing, using or managing automated testing. Testers, analysts, developers, automators and automation structures, test managers, project managers, QA experts, and technical directors will benefit from reading books. this book.

Link: Experiances of Test Automation

6. Agile Lean ATDD

In the framework of Acceptance Test-Driven-Development (ATDD), customers, developers, and testers work together to create acceptance tests to fully interpret the software that needs to work. how, from the customer's perspective.

By tightening the relationship between customers and agile teams, ATDD can improve both software quality and development performance significantly.

“This book provides clear, direct guidance on how to use the business-facing test to navigate software development. I am excited for the excellent knowledge in this book. It is a great combination of author's experience, references to other experts and research, and a sample project that covers many aspects of ATDD. A wide range of readers will learn a great deal, whether they work on lean or agile projects or simply want to deliver the best software product possible. ”


  • How to develop software with full testable requirements
  • How to simplify and divide the tests and use them to find the missing logic
  • How to test the user interface, service implementation, or difficult components of a software system
  • How to format the request that can best be handled outside the software
  • How to give test results, evaluate them and use them to overall assess the progress of the project
  • How to build acceptance test creates mutual benefits for the development organization and its customers
  • How to expand ATDD for big projects

Link: Agile Lean ATDD

7. The Cucumber Book

If you are a tester in agile team, chances are you have already done the acceptance test of the user stories you want to automate. This book teaches you the basics of BDD, how to write Gherkin correctly and in a format that is easy to understand, even on your automated tests.

You will learn how to use Cucumber's Gherkin DSL to describe in simple language – the behavior your customers want from the system.

This book will show you how to express your customers' ideas into a clear, workable specification that everyone on the team can read. You will learn how to apply these examples in Cucumber. You will build the right code to make your customers happy, not one more line.

Written by the creator of Cucumber and one of the most experienced users and contributors, the Cucumber book is a guide that gives you and your team the knowledge you need to confidently start using it. Cucumber.

Link: Cucumber

8. Explore It!

In agile projects, discovery testing is often considered an additional testing process for automated testing. Actually testing discovering more bugs than other testing methods.

Software programming always hides surprises. No matter how good you are, when you create a software it's always possible it will behave differently than expected. Discovery testing contributes to reducing those risks.

This book helps you learn the core skills of discovery, including how to analyze software and point out key failure points, how to design experiments immediately, and ways to sharpen critical skills. and how to focus on the target.

Part 1 introduces the core and important skills of discovery testing

Part 2 continues to build on this foundation

Part 3 introduces techniques to the software development environment

9. Agile Tester – One for all, All for one

This book is about the basic knowledge of ISTQB Agile Test Foundation. It is a complete study material and will prepare you for the certification exams.

Software development with agile

The basic principles, applications and processes of agile testing

Agile testing methods, techniques and tools

The book also contains the knowledge to get an International Agile Tester Foundation certification on, an emerging learning path around the world. This route has a lower test fee and allows home-based implementation. Link: Agile Tester – One for all, All for one

10. Lessons Learned in Software Testing

And last but not least … The book every tester should read. This book contains over 200 lessons learned from over 30 years of combined testing experience.

Each lesson is an assertion related to software testing, followed by an explanation or example that shows you how, when and why.

Not only are tips, tricks and traps to avoid, lessons learned in software testing help you pass the important testing phase of a software development project without having to go through the testing process and errors that it usually has to make.

The ultimate resource for testers at all levels of expertise.

Share the news now

Source : TechTalk