If we will have workflow based on Pull Requests that is great!
On wiki there is a section:
Code review policy
It doesn't mention anything about manual testing. It is common practice (at least in projects in which I worked on) to test each PR (or "each story" like we like to call it) separately. This helps keep main branch stable, what helps in development and makes deployment almost painless.
One of the reviewers may be the author of the change.
I am not sure, whether I understand. Are you suggesting, that developer could make a "self-code-review" in this workflow?
I suggest to require at least 2 reviewers (each has to give "OK" ) and "
QA Done" from tester. Like here:
OK... you may say, that you don't have enough testers.. what is not true. I suggest to give a chance a community. I would like to help you with simple fixes and with testing...and I am sure, that there is a lot of guys like me here.
You might also think, that it would be difficult to coordinate all of that.
I have already suggested to use gitter for that: