Does a pull request review consist of testing, code review or both and how long should the average PR take?
I don't know whether the testing just involves testing the functionality that's been altered, or thoroughly testing the whole app and what purpose this has if the author has already tested this.
If it involves a code review should it be a brief glance over within github or a thorough review including a parse through the code in action within your chosen IDE.
I'm part of a paid development team where 100% of our PRs come from our team.
Does a pull request review consist of testing, code review or both-- A review consists of whatever the reviewer needs to do to determine that the change is suitable to incorporate into the main branch. Questions they might as are: Is this change useful? Is it consistent with the rest of the project? Does it work? Does it fulfill our design principles? Your set of questions might be different.