Assuming an iteration between two and four weeks:
1) Programmers will write unit tests in the code to ensure product technically behaves. The team will perform QA activities to ensure these are valid tests.
2) In the iteration planning meeting and in the iteration itself, tests cases will be defined as acceptance criteria for each product backlog item/requirement.
3) Acceptance criteria will be implemented as automated tests.
4) Every code check-in on the release branch will trigger all automated (unit and functional) tests to run as to perform full automated regression tests.
5) Tests will be implemented in the iteration where the requirement is being built.
6) Tools for performance, load and security tests will run at the end of each iteration.
7) Manual exploratory testing will be done at the end of an iteration in an attempt to identify missed tested cases.
8) At the iteration review meeting, stakeholders will verify that the solution is what they envisioned and will give feedback for the next iteration(s).
9) After deployment into production, you can implement A/B testing and review your product analytics to look at how users actually use your new functionality.
Originally published at https://www.henricodolfing.com.