This video takes a detailed look at coded UI tests,which can be used to create fully automated UI tests for Microsoft Silverlight, Windows Forms, Windows Presentation Foundation (WPF), and web applications. Learn some techniques for creating robust coded UI tests which can be maintained over time along with your evolving application.
This blog post presents the changes to unit testing made in the new version of Visual Studio. The Test View and Test Results windows have been replaced by the Unit Test Explorer, a new user interface that let developers quickly interact with their tests. Third party test frameworks are supported by a new test meta-runner that coordinates and controls the flow of data between the user interface and the underlying test frameworks. Visual Studio will also provide a true native unit testing framework for C/C++. A new test isolation and stubbing framework for managed .NET code called Visual Studio Fakes has been added. A new feature allows also to tests after each successful build. Some Visual Studio 2010 test features have been removed.
This blog post provides a detail process on how to write acceptance tests for the UI using Visual Studio 2010 Microsoft Test Manager and Fit style tables. Fit tables, originally defined for the fitnesse open source software testing tool, allow stakeholders and business analysts to enter expected input and the proper output in a tool they are comfortable wit, like word processor or a spreadsheet.
This article provides a process to integrate Test-Driven Development in the maintenance of a .NET application. You will first write the tests that will prove your new code gets the same results as the legacy code. Then you isolate new code into separate methods or classes that you can test independently. You break down the requirements into simple valid tests. Finally you check to see that you have not introduced a new bug. While you are doing this, let Visual Studio generate the utility code for you and find a tool to run your tests continuously like AutoTest.NET.
This video describes the six mechanisms in Visual Studio 2010 that enable more effective collaboration between developers and testers. These mechanisms include tools to create actionable bugs, debug historical events, and automate functional testing. Effective collaboration between developers and testers is paramount and can make the difference between shipping quality applications on time, or slipping because bugs are found late.
Have you visited the treasures of Visual Studio Menu bar tools | Options | Test Tools lately? The options to enable disable prompts on creating, editing, deleting or running manual/automated tests can be controller from here. The default test project language and default test types created on a new test project creation could be selected/unselected from here.
Load testing is almost always conducted to address one or more risks related to expense, opportunity costs, continuity, and/or corporate reputation. In two blog posts, Tarun Arora discusses the topic. In part 1, he explains why Performance Testing the application is important, presents the test tools available in Visual Studio Ultimate 2010 and various test rig topologies. In part 2, he analyzes the details of web performance and load tests as well as why it’s important to follow a goal based pattern while performance testing your application.