AB Testing – Episode 77: The Conception of the Modern Testing Principles

We discuss, vet, and rewrite (and not for the last time), the Modern Testing Principles. These are a work in progress, but we’re happy to share the current final form.

Listen to the podcast to hear these developed in real time.

  1. The customer is the only one suitable to judge and evaluate the quality of our software
  2. We apply the theory of constraints to identify, prioritize and mitigate bottlenecks from the system (and accelerate the team).
  3. We are not the safety net for software correctness – we focus on improving the business, and not the code.
  4. We are responsible for the quality culture of our team, and are accountable for helping and coaching the team in this regard.
  5. We use data to deeply understand customer usage and customer pain.
  6. Embrace continuous improvement, and help the team adapt and optimize in order to solve customer pain
  7. We strive to reduce or eliminate the need for a dedicated testing specialist on our teams by increasing testing abilities and knowhow across the team.

7 thoughts on “AB Testing – Episode 77: The Conception of the Modern Testing Principles

  1. Quality Assessment regences the process and product.
    Testing adds value to the product and team by helping teams to understand the value of the product. For example, it indicates the non monetary costs to the stakeholders: users, customers, etc. For example, data corruption, complicated workflows, inaccurate messages from the product.

  2. I always feel a little sad when people advocate for the removal of dedicated testers.

    We strive to reduce or eliminate the need for a dedicated testing specialist on our teams by increasing testing abilities and knowhow across the team.

    1. We’ve updated that one to show that the removal of a testing specialist is one outcome of a team following Modern Testing principles

Comments are closed.