I recently tried to convert some NUnit tests to VSTS using Jim Newkirk's converter posted on GotDotNet. It had been awhile since I tried it and I had forgotten an important detail... The add-in is based on the Guidance Automation Extentions which were previewed against Beta 2 and haven't been updated yet. That means you can't use the converter on a VSTS Beta 3 Refresh/RTM setup.
I spent about an hour and successfully converted the test project manually. It would've taken about 10 minutes if I had just followed the directions that Susan Entwisle posted in her blog.
If you do decide to convert NUnit tests to VSTS, don't be afraid to do it manually. The process is relatively painless with strategic use of Search/Replace over the entire test project.
This past week I had the ability to do some performance testing on Team Foundation Version Control and a Proxy server over a corporate WAN. I was told that our test case used to take 20-25 minutes when doing a "Get Latest" between the US-based server and the India-based workstations. That was significantly improved to about 5 minutes when they went to SourceOffSite. (If you don't have an option to use Team System and are trying to use VSS over a WAN, you should at least take a look at SourceOffSite.)
Now for the measurements that I actually observed... Using Visual Studio 2005 with Team Explorer, the same test case took about 2 minutes. We added a proxy server in India and further reduced the time to ~45 seconds (after the proxy was populated).
Of course you mileage may vary, but I'm still excited to see a standard development task that apparently took 20+ minutes dropped to 45 seconds using Team System! I'm equally impressed by how well the system performed even without the proxy! I think this is a testament to how well the TFVC team did when architecting the system for distributed team development.
If you haven't already attended one of these chats and are otherwise interested in VSTS, I encourage you to give it a check. The price is right and they are low impact. You can easily have a browser up tuned into the chat in one window and half follow along while you develop in in another window. You don't need massive bandwidth to partake and since it is an interactive chat, you really can get your questions answered. Enjoy...
Team System MSDN Public Chat
Visual Studio Team Edition for Software Developer &
Visual Studio Team Edition for Software Testers
When: Wednesday, November 16th @ 10am PST
What: Join us to discuss the Profiler, Test Tools (Unit, Generic, Manual), Web & Load Testing, and Code Analysis (FxCop & PREFast). We have questions for you, will answer questions from you, and will chat about the exciting new technology.