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 20:48, 13 July 2011
, 13 July 2011→Risks & Plans & Tools
| Line 46: | Line 46: | ||
** Community involvement will be a key component to alerting the team to any issues which appear in production. We are currently developing plans to encourage user SUMO feedback. Examples include adding a feedback button on each page, similar to Get Satisfaction. There is a plan to bring in UX people to discuss. This will provide an active feedback system to complement the passive monitoring tool feedback. | ** Community involvement will be a key component to alerting the team to any issues which appear in production. We are currently developing plans to encourage user SUMO feedback. Examples include adding a feedback button on each page, similar to Get Satisfaction. There is a plan to bring in UX people to discuss. This will provide an active feedback system to complement the passive monitoring tool feedback. | ||
** There is a general increased risk with less manual testing. The compensation for that is more data measurement, faster fixes, and more time for QA to work in other areas. | ** There is a general increased risk with less manual testing. The compensation for that is more data measurement, faster fixes, and more time for QA to work in other areas. | ||
** Code reviews are already mandatory for developers. Smaller releases make issues easier to determine and easier to resolve. There will be mistakes but everyone will learn quickly from them. | |||
* Risk: Cannot test notifications | * Risk: Cannot test notifications | ||