I'm didn't understand: when functional testing begin in MSF, in stabilizing or in developing phase? And what about testing daily bilds: is it Unit testing or testers day by day check the same functionality? [img]images/icons/wink.gif[/img]
That is up to you and your test department. MSF if just a guideline, not a process. You can begin testing during the development phase, or the stabilizing phase. The development phase would be considered a QA effort where the stabilization phase would be more of a QC effort.
Look at it this way. The testing effort will begin when the project begins. You should be involved with the 'Team' early on so you can do the Requirements Review, Design Review, early Test Planning. These are 'testing' tasks that need to be done in the early phases (Requirements Gathering, Design & Code) along with the Construction (Integration & System Testing) and Implementation (UAT) phases of the MSF model.
As Rich said, MSF is a guideline (Framework) that you and your company have to 'fit' to their needs and follow the process/methodology you have implemented based on that guideline. One thing to note, you will need all parties involved (Development, Marketing/Sales, Support, Proj. Mgt., Executive Mgmt., and Test/QA) to 'buy-in' and support it. Otherwise you run a risk of problems and eventual failure.
I have been in a couple of companies that used MSF. One succeeded because we had full buy-in, the other failed because it was just given lip service by most groups (parts of Dev. & Test bought in, but others did not).