In my opinion, if the test team doesn't possess the skills to understand or maintain the harness and/or tests, they logically belong in a group that does.
I would say there is nothing to be wary of in this case; in most companies for which I've worked, development is free to run whatever tests they feel necessary during unit testing. When the application(s) are turned over to QA, we will run our own bank of tests and see how a good a job they did [img]/images/graemlins/smile.gif[/img].
Ideally its Development but nowdays its changing to QA teams. Many teams the team has to comprise of Black Box Testers + White box testers nowdays. With Unit test on QA side I agree it takes more time to get the release out but the time where designing of software is done, the same time can be utilized to get the unit test set up ready.
ALso with unit testing knowledge the testers have a ebtter understanding of the application as they now know at code level.
Wow, this is a popular topic. In fact, 4 of the last 8 topics in this forum have covered it. Rather than repeat what was said there, I will just provide the links to the other three. They should be fairly informative for your needs.