Quotes & Notes on “Agile Testing Condensed: A Brief Introduction” by Janet Gregory and Lisa Crispin

The book: Agile Testing Condensed: A Brief Introduction

The authors: Janet Gregory & Lisa Crispin

Collaborative testing practices that occur continuously, from inception to delivery and beyond, supporting frequent delivery of value for our customers. Testing activities focus on building quality into the product, using fast feedback loops to validate our understanding. The practices strengthen and support the idea of whole-team responsibility for quality.

This is the authors’ definition of Agile Testing. To me, the biggest differentiator from other testing definitions is that this one promotes to actively improve quality rather than only inform on the status of quality.

When the whole team is responsible for quality of the product as well as quality of the process, each team member needs to be proactive in solving problems.

Quality coaches might educate, prepare or motivate team members to become proactive.

There are many things to consider around your product domain. It is not only the software you are testing; it is the product that your end users depend on.

I find this advice needs to hold true for anyone working in software development.

Read More »

Keeping Up with Compliance in a DevOps World

This post first appeared at the DevTestOps community on October 4, 2019.

About 5 years ago I was working in a small product that was doing (almost) everything the DevOps way. We had the works: code and tests versioned in git, trunk based development, building the code once (more or less), feature toggles, daily deployments, the ability to fix issues fast, monitoring and alerting of our production system.

But there was one tiny problem.

We still needed to adhere to the company’s Quality Management System (QMS) which included compliance to ISO 9001 certification as well as other regulatory requirements. While development was adapting to the new world in a fast pace, the same could not be said for the company’s processes at that time.

So here are some things we did to address the situation.

Continue reading at the DevTestOps Community