Search

Unit Testing Slow 2 by Kristofer Liljeblad

Closed
as Fixed Help for as Fixed

21
Sign in to vote
1
Sign in to vote
Sign in
to vote
Type: Bug
ID: 119317
Opened: 5/13/2005 12:37:33 AM
Access Restriction: Public
0
Workaround(s)
16
User(s) can reproduce this bug
According to FDBK19987 (Unit Testing Slow) so are you supposed to reduce overhead in unit testing and optimize performance to Visual Studio 2005 Team System Beta 2, but that is not done or not enough. FDBK19987 is now closed, but the issue is not fixed.

Try the open source alternative nUnit and compare the difference in speed.

nUnit is so much faster that we probably will have to go with nUnit instead of VS Team System for Unit Testing.
Details (expand)
Product Language
English
Version
Visual Studio 2005 Beta 2
Category
Unit Testing
Operating System
Windows XP Professional
Operating System Language
Swedish
Steps to Reproduce
Create some simple tests in Visual Studio 2005 Team System Beta 2 and run them from inside Visual Studio and from the nUnit GUI and compare the difference in speed.
Actual Results
nUnit is much faster than Visual Studio.
Expected Results
Visual Studio should be as fast or faster than nUnit.
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 5/24/2005 at 1:13 PM
Thank you for reporting this issue. This is definitely a known problem that we're working on fixing prior to RTM. One of the things that affects speed is the way that we run tests. That is, we run each test in its own process so that if it ends up crashing, it won't take the IDE down with it. We're working on speeding up execution while continuing to give the user the flexibility of not crashing their IDE.

Thanks gang. We hear you on this one. Please keep sending this type of critical feedback.

Tom Arnold
PM, VSTT
Posted by Microsoft on 6/29/2005 at 12:49 PM
Thank you for the feedback. We have addressed performance issues in our internal post-beta2 builds.

Tom Arnold
PM, VSTEST