Page History
...
If you're following Agile, namely Scrum, you'll have sprints of one or more weeks, where each one represents one iteration where at the end you have a shippable product. Testing can occur hopefuly during the period of the sprint or more closely to the end of it. In any case, you can have a Test Plan per sprint to track the results of the Tests you want to execute, including the ones that validate the features implemented in that sprint. Besides this, you may also want to have a Test Plan related with regression testing to ensure you're not braking anything in the sprint.
| Info | ||
|---|---|---|
| ||
A sprint is a more manageable way of dividing the complexity of a whole release. A sprint has a well known, not that long, time period. |
Kanban
In Kanban you're limiting the amount of WIP issues in a given state, namely the ones that are in testing. As you're not dividing your release in several periods of time, as you do with Scrum, you can manage it as if the period of it would embrace the time frame of the release.
Thus, you can have a Test Plan to track the Tests related with the features being addressed in the Kanban board. Besides it you may complement it with additional Test Plans, namely for tracking the regression testing. As in Kanban you're delivering features any time soon, it may be a good approach to have the Test Plan with regression tests, or smoke tests, as an independent Test Plan, so it is more clear if regressions are arising or not.
Waterfall
In this scenario, testing is done as a separate phase at the end of development. From the testing bugs may be found which will lead to go back to the requirements analysis/development, wait for changes/fixes to be made and then test it once again.
...