Difference between revisions of "Code Review Workflow"
From Agility
(Created page with "# We are using Crucible software for code review and also for general review of non svn tasks (if required) # Our workflow is based on [https://confluence.atlassian.com/crucib...") |
|||
| Line 1: | Line 1: | ||
| − | + | <ul> | |
| − | + | <li>We are using Crucible software for code review and also for general review of non svn tasks (if required)</li> | |
| − | + | <li>Our workflow is based on [https://confluence.atlassian.com/crucible/the-crucible-workflow-298977485.html One-to-One Reviews] (without moderator). | |
| − | + | ||
| − | + | [[File:onetooneworkflow.png]]</li> | |
| − | + | ||
| − | + | <li>Responsibility of task owner (developer / tester) is to create review and assign to it Reviewer</li> | |
| + | <li>There is no general rule for Reviewer selection it is agreement between Task Owner and Reviewer (agreement can be made on Daily)</li> | ||
| + | <li>After positive review (or settlement with Reviewer ;-) : | ||
| + | *Reviewer complete review | ||
| + | *Author close review | ||
| + | </li> | ||
Revision as of 07:19, 13 October 2017
- We are using Crucible software for code review and also for general review of non svn tasks (if required)
- Our workflow is based on One-to-One Reviews (without moderator).
- Responsibility of task owner (developer / tester) is to create review and assign to it Reviewer
- There is no general rule for Reviewer selection it is agreement between Task Owner and Reviewer (agreement can be made on Daily)
- After positive review (or settlement with Reviewer ;-) :
- Reviewer complete review
- Author close review
