In traditional waterfall and agile processes we implement a test strategy to set expectations (and receive feedback) on approach for a release (multiple sprints of work) and test summary to capture results of the execution (functionl, security, and performance testing).
In a a CI/CD model when we have a 2 week sprint and plan to deploy every 2 weeks it seems a bit cumbersome to do a strategy and summary every 2 weeks. Ideally the summary could be pulled from an automation tool and produced to a dashboard so that should not be too bad.
Is there a different approach to the strategy?
Are there other quality tollgates (maybe a bad choice of words) that we should consider?
From a quality process audit perspective is there anything else to consider?
Any feedack appreciated.
-Jeff
