Test plans are something that come up a lot. People ask on different forums what a software test plan is, how do you write one, what should go into one, etc.
@rocketbootkid recently wrote an article for the Dojo “How To Write A Software Test Plan: Learning What’s Important And Where To Start”.
During our 30 Days of Agile Testing challenge, @jesper posted about what his test plans look like 30 days of Agile Testing, Day 26: What does your Test Plan look like? I think this ties in well with the article from Richard, test plans can take many different formats depending on your environment, audience, etc.
One question I often hear asked is “What should be in a software test plan?”. Again, this is something that will depend on your situation, audience and possibly even your tech stack but what advice would you give? What do you think should be in a software test plan?