In my team I have applied a culture of code review and feature review.
The code might look great, written spectacularly, however the feature might not work.
It seems to me as 2 different scopes for review. While code reviews require a very technical and in depth knowledge, feature review requires only familiarity with the spec.
When I google code review I get a bunch of results. However can't find anything on any other kind of review.
A brief reference can be found at https://softwareengineering.stackexchange.com/a/92417/95463 where BillThor says "You were asked to review the code do so, it is not the same as testing it"..
Do you use other kind of reviews and what are their goals and process?
We use a feature review where someone is actually running the tests and the feature manually and verifies it is intuitive and applies to spec.