I am a developer and I generally check in partial implementations so that I don't have too much uncommited code at any time. I make sure that the application compiles and that it does not interfere with other parts of the code. Only when I have implemented and tested a feature do I mark it as "done". This is when I feel that SQA can formally start testing the feature. Lately our SQA has been told to start testing things and logging bugs that are not fully implemented yet. To make matters worse we have 3 SQA and they all log the same bug. This increases the number of bugs that get assigned to every developer and then not only do the developers have to complete the task on hand but they also have to work through all these bugs that have been logged. For me personally when I get 20 bugs on any feature I feel as though I did a sloppy job. Is this a normal/accepted practice?

I am a developer and I generally check in partial implementations so that I don't have too much uncommited code at any time. 

I make sure that the application compiles and that it does not interfere with other parts of the code. Only when I have implemented and tested a feature do I mark it as "done". This is when I feel that SQA can formally start testing the feature. 

Lately our SQA has been told to start testing things and logging bugs that are not fully implemented yet. To make matters worse we have 3 SQA and they all log the same bug. 

This increases the number of bugs that get assigned to every developer and then not only do the developers have to complete the task on hand but they also have to work through all these bugs that have been logged. 

For me personally when I get 20 bugs on any feature I feel as though I did a sloppy job. 

Is this a normal/accepted practice?