This week, I have taken the inspiration from discussions at FroGSConf last week, and worked on my test plans. And today, I am ready to share that instead of creating one plan, I created three - I call this the power of three. Very often different things will serve you best for what you are trying to plan for, and for the things I wanted, I couldn't do with one.
The 1A4 Master Test Plan
The first plan I created was a master test plan. Where I work, we have this fairly elaborate template from the times when projects were large and not done in an agile fashion. That plan format overemphasized thinking of details prematurely, but has good ideas behind it, like understanding the relationship of different kinds of testing we will or will not do.
Analyzing it, I could condense the relevant part of the plans into one A4 with many things that are specific to the fact that we are building embedded systems.
- Quality Target describes the general ideas about the product that drive our idea of how we think around quality for this product.
- Software Unit & Integration Testing describes the developer-oriented quality practices we choose from generally.
- Hardware Testing addresses the fact that there is a significant overlap and dependency we should have conversations on between hardware and system testing.
- System Testing looks at integrated features running on realistic hardware, becoming incrementally more complete in agile projects.
- Production Testing addresses the perspectives of hardware being individuals with particular failure modes, and something in assembly of a system, we have customer-specific perspectives to have conversations on.
- The 1A4 master test plan
- The system test strategy
- The test environment plan