Confirmed users
1,504
edits
QA/Execution/Web Testing/Continuous Deployment: Difference between revisions
QA/Execution/Web Testing/Continuous Deployment (view source)
Revision as of 01:47, 13 July 2011
, 13 July 2011→Changes
| Line 26: | Line 26: | ||
*We could have more tests run in production, although only ones that do not create or destroy content. It is important not to create unnecessary data, and to avoid sending out notifications. Features are fully tested after each check-in. | *We could have more tests run in production, although only ones that do not create or destroy content. It is important not to create unnecessary data, and to avoid sending out notifications. Features are fully tested after each check-in. | ||
3. Releases | |||
* Will go out as many times as there are fixes ready to go. They will be released by developers, without IT or QA. The developers will be in charge of monitoring services after the release to watch for changes in behavior. | |||
4. Bug fixes: | 4. Bug fixes: | ||
* Do not need verification prior to releases. They may be verified by a developer, or by QA in production. | |||
5. New features: | 5. New features: | ||
* Do not need verification prior to release. They may be released to production under flags. Flags are already used in production | |||
==Risks & Plans & Tools== | ==Risks & Plans & Tools== | ||