Leveraging a good domain model to create a quality assurance program from scratch

At chef.io, we are building a new platform for DevSecOps – before we could start, we needed to analyze our domain and the changes we wanted to make in the next generation of services. DevSecOps is a domain many of us know implicitly through using common tools, so we’ll look inside this domain and how we’ve modelled these distributed services and agents. Next, we’ll look at the value propositions contained within the model and analyze the alignment with business scenarios. With audience engagement, we will use the quality bar for the project and develop the test plan and key test cases for the domain together. We’ll wrap up with a discussion of how to migrate from unit tests to true end-to-end scenario testing, selection of automated and manual testing tools, a couple practical release readiness checklists, and survey the lessons learned from growing our QA program. This case study will explore how to put a quality testing approach in place – especially for organizations which have relied exclusively on automated tools and have low maturity in manual scenario testing or have distrust between the business and engineering on testability – and verify quality attributes in the domain model. We anticipate having at least three points for incorporating participants’ own experiences as we go through this session.

Prerequisites

Understanding of requirements for a distributed (multi-service, multi-application) system. Basic application of quality attributes or non-functional requirements. Conceptual understanding of BDD or TDD (or QA approaches in general) Ability to use Miro or similar brainstorming tool (will be provided)