In this month's column Dr. James McCaffrey describes some of the ways you can use the Visual Studio 2005 Team System to manage custom software test automation.
Dr. James McCaffrey
MSDN Magazine Launch 2008
View Complete Post
Dan Griffin shows the extensibility of Visual Studio 2005 Team Edition for Software Testers by discussing the modification of the existing Test Interface Provider sample in the latest Visual Studio SDK and implements Fuzz Testing.
MSDN Magazine November 2007
This article discusses a new load test tool in Visual Studio 2005 Team System for performance and stress testing your Web sites, Web services, and other server components. Combined with its handy reporting capabilities, the load test tool provides some powerful options for sharing and managing test results.
MSDN Magazine June 2006
MSDN Magazine January 2010
Here we show you how to use Windows PowerShell to create quick and easy UI test automation for ASP.NET and classic ASP Web applications.
MSDN Magazine March 2008
James McCaffrey shows you how to get started with UI test automation using the new Microsoft UI Automation library.
MSDN Magazine February 2008
This installment of Test Run is a guide to using Windows PowerShell to perform ultra lightweight UI automation.
MSDN Magazine December 2007
Team Foundation Server provides APIs that let you create check-in notes (categorized string data) and custom check-in policy implementations. These features combine to give project administrators better control over the group development process.
Brian A. Randell
This month's column explores how to create lightweight but powerful UI test automation for software systems that run on Windows XP Embedded.
Dr. James McCaffrey and Mike Hall
MSDN Magazine October 2007
MSDN Magazine March 2007
This month James McCaffrey presents a technique that allows you to write lightweight test automation to verify the functionality of AJAX Web applications.
MSDN Magazine February 2007
As Web applications have become more complex, testing them has become more important. There are many testing techniques available to you. For example, in the April 2005 issue of MSDNÃÂ®Magazine, I describe a simple JScriptÃÂ®-based system that can test a Web app through its UI by using the Internet Explorer Document Object Model.
MSDN Magazine October 2005
There are several ways to test a WindowsÃÂ®-based application through its user interface. For example, in the January 2005 issue of MSDNÃÂ®Magazine (Test Run: Lightweight UI Test Automation with . NET) I described a lightweight technique for testing .
MSDN Magazine September 2005
The release of ASP. NET revolutionized Web development and made it easy to create full-featured Web applications. Visual StudioÃÂ® 2005 and ASP. NET 2. 0 will let you add even more functionality to your applications, but the more features a Web application has, the more important testing becomes.
MSDN Magazine April 2005
Manual user interface testing is one of the most fundamental types of software testing and it's the kind of testing that most software engineers first experience. Paradoxically, automated user interface tests are probably the most technically challenging kind of test to write.
MSDN Magazine January 2005
The most fundamental type of software test automation is automated API testing. API testing essentially entails testing the individual methods that make up a software system rather than testing the overall system itself.
MSDN Magazine November 2004
If you're encrypting user data with Secure Sockets Layer (SSL) over HTTP and you want to test your Web applications programmatically you'll find that the techniques are not widely known. In this month's column I'll show you how to set up a test SSL server and write test automation that verifies the functionality of a simple but representative Web application.
MSDN Magazine August 2004
The .NET Framework provides a surprising new way to quickly and easily create user interface test automation. By using objects in the System.Reflection and System.Threading namespaces, you can write automated tests in minutes instead of hours. This article walks you through the building of a typical Windows-based application that will be used as the test subject. The author then runs through the creation of a C#-based test tool that simulates clicking the test app's UI controls and checks the application's state. After the tool is built, the author explains in detail how it works so you can modify and extend it for your own use.
MSDN Magazine January 2003