Friday, November 11, 2005

A very nice set of articles that talks about testing of Whidbey. Excellent read. Enjoy!!!!

Testing ASP.NET 2.0 and Visual Web Developer
Summary:
Several people have asked for additional testing details after my recent Whidbey Update post where I talked a little about how we are building ASP.NET 2.0 and Visual Web Developer. Some specific questions I’ve been asked include: How do you build and track 105,000 test cases and 505,000 test scenarios? How big is the test team in relation to the dev team? What tools do we use to write and run them? What is the process used to manage all of this? Etc, Etc. Hopefully the below post provide some answers.

Sample documents (Read article first)
Sample Test Plan:
http://www.scottgu.com/blogposts/testingatmicrosoft/testplan/testplan.htm
Sample Automated Test Case:
http://www.scottgu.com/blogposts/testingatmicrosoft/testcase/testcase.htm


Tracking Bugs
Summary:
“Can you clarify - how issues are assigned to developers? Does a tester assign issues directly to members of development team, or they assign them to PM who will assign those issues to team members? Or issues are automatically distributed between development groups based on member's workload? What kind of software do you use for issue tracking?”

What Great .NET Developers Ought To Know

Test your expertise in .NET with this questionnaire. This is used internally in MS for interviews. http://www.hanselman.com/blog/WhatGreatNETDevelopersOughtToKnowMoreNETInterviewQuestions.aspx

Tim Heuer, inspired by “What Great .NET Developers Ought to Know”, came up with his own SharePoint version:
what a good sharepoint subject matter expert ought to know...

Monday, November 07, 2005

Cyclomatic Code Complexity Analysis for Microsoft .NET Applications

Please find more information regarding the Cyclomatic Code Complexity Analysis for source code for .NET and VS 2005

Cyclomatic Code Complexity Analysis for Microsoft .NET Applications
http://www.codeproject.com/dotnet/Cyclomatic_Complexity.asp

CA1502: Avoid Excessive complexity - Code analysis rule in VS2005
http://bloggingabout.net/blogs/erwyn/archive/2005/11/04/10140.aspx

The inner works of code coverage instrumentation in VS Team System
http://dotnetjunkies.com/WebLog/anoras/archive/2004/09/20/26199.aspx

Cyclomatic code complexity analysis is supported in FxCop that is integrated with VS 2005 (not in the standalone free tool). The rule reports a violation when the cyclomatic complexity is greater than 25 (which cannot be changed) which sucks