I'm calling it quality advocacy to prevent it from turning into a manual-test-at-the-end-road-block. If you need some background on what a quality advocate is, have a look at this description from Alister Scott, or this one from Menlo Innovations.
We are working on TDD and BDD, with Quality advocates helping to define good requirements (including meeting with actual customers and end users), helping developers come up with good unit tests and coding standards, and basically get all of the testing done withquality high before check in.
We are using C#/NUnit and AngularJS/JQuery/HTML5/Jasmine/Karma on the dev side, Cucumber/Ruby on the Gui test side.
If you are interested, have a look at the job posting