Come up with a basic test plan template for a feature

We should be documenting test plans for test features to be carried out and linked to the epic/requirements. The test plan should be roughly consistent across the teams with owners/execution steps, risk management and etc.

A few options to consider:

• Mek’s legacy version: https://gitlab.com/gitlab-org/quality/team-tasks/snippets/1742002
• Light weight version with GDPR: gitlab-org/release/tasks#172 (closed)
• GCP Migration (whole company event type)
  • Initial: gitlab-com/migration#330 (closed)
  • Follow up: gitlab-com/migration#451 (closed)
  • Spreadsheets: https://drive.google.com/drive/folders/1UBHpy4B0mhzsswJmPFahlf4bgSeYiViO
• Google’s ACC method or 5 min test plan.
  • https://testing.googleblog.com/2011/09/10-minute-test-plan.html
  • ACC Framework
    • https://testing.googleblog.com/2011/10/google-test-analytics-now-in-open.html
    • https://code.google.com/archive/p/test-analytics/wikis/AccExplained.wiki
    • https://sites.google.com/site/visualisingquality/techniques
    • https://www.slideshare.net/99tests/how-to-log-bugs-the-google-way-the-acc-methodology

Supplemental reading:

• https://gojko.net/2010/10/15/how-google-does-test-engineering/
  • This person wrote the book on 50 ways to improve tests.
• 50 IDEAS to improve your tests
  • Sharing conversation: https://gitlab.slack.com/archives/C3JJET4Q6/p1526529981000111
  • File https://gitlab.slack.com/files/U9MSQ7474/FAQP45A9F/50-quick-ideas-to-improve-tests.pdf
  •