How Do I Create a Breakpoint Using Conditions?

Published February 16th, 2010 Under Software Testing | Leave a Comment

There are many ways to create breakpoints. By default, a breakpoint is triggered each time a line of code is reached. This video demonstrates how to use advanced breakpoints to only trigger when certain conditions are met.

http://msdn.microsoft.com/en-gb/vstudio/dd442440.aspx

Learn Tips and Tricks for Debugging in Visual Studio

Published December 28th, 2009 Under Software Testing | Leave a Comment

In a debugging session, it is possible to view and explore the values of elements. It is also possible to modify those values in an effort to determine how a new value affects the outcome. In this video, Todd Miranda demonstrates how to use watch and immediate windows to test various scenarios while debugging.

http://msdn.microsoft.com/en-gb/vstudio/dd442479.aspx

10-4 Episode 18: Functional UI Testing

Published September 1st, 2009 Under Functional Testing, Software Testing | Leave a Comment

In this episode of 10-4 we look at a new type of test coming in Visual Studio Team System 2010 known as the coded UI test. Coded UI tests can be created to automatically navigate through your application’s UI, which in turn can be used to verify that the paths your users might take through your application are working properly. You can also add validation logic along the way to verify the properties of objects within the UI. Much like unit tests can quickly surface regressions on a method or function level, coded UI tests can bring the same level of rapid automated testing capabilities to the UI layer.This demo is based on an early build of Visual Studio Team System 2010 Beta 1.

For some relevant team blogs check out:
Amit Chatterjee’s Blog: http://blogs.msdn.com/amit_chatterjee/
Mathew Aniyan’s Blog: http://blogs.msdn.com/mathew_aniyan/


Get Microsoft Silverlight

Getting started with Pex in Visual Studio 2008

Published August 24th, 2009 Under Unit Testing | Leave a Comment

Nikolai Tillmann and Peli de Halleux give a short tutorial on Pex, an automated white box testing tool for .Net. The tutorial is a pair-programming session where they show us how to get started with Pex in Visual Studio, starting from an (untested) piece of C# code:
* how to use Pex to explore the behavior of any method in your code,
* how to save the exploration results into a unit test suite,
* how to improve the generated parameterized unit tests to leverage Pex code exploration engine.
If you want to follow up the steps on your machine as well,
* Download Pex from DevLabs
* Download the code example
* Ask your questions in the forum


Get Microsoft Silverlight

Pex – Automated Exploratory Testing for .NET

Published August 21st, 2009 Under Unit Testing | Leave a Comment

Pex is a white-box test generation tool for .NET. Starting from a hand-written parameterized unit test, Pex analyzes the program-under-test to determine relevant test inputs fully automatically. To this end, Pex executes the program multiple times with different inputs while monitoring the taken execution paths. Pex uses a constraint solver to determine new test inputs that will exercise different execution paths. As a side effect, Pex may find errors in the program. The result is a traditional unit test suite with high code coverage. In addition, Pex suggests to the programmer how to fix certain errors. Pex is integrated into Microsoft Visual Studio.

Refactoring Unit Tests Part 2 Using Object Builder Pattern

Published June 4th, 2009 Under Unit Testing | Leave a Comment

In this screencast we will demonstrate how to use the Object Builder pattern to create and setup objects for tests. In the first part we discussed how to introduce the base class for the unit tests to improve readability and cleanness of code.

http://highoncoding.com/Articles/443_Refactoring_Unit_Tests_Part_2_Using_Object_Builder_Pattern.aspx

Refactoring Unit Tests Part 1

Published June 4th, 2009 Under Unit Testing | Leave a Comment

In this screencast we will refactor unit tests to make it more readable. It is very important that you refactor your unit tests. Unit test code is not part of the production but refactoring them can help you in the long run and will provide benefits when maintaining the application.

http://highoncoding.com/Articles/442_Refactoring_Unit_Tests_Part_1.aspx

« go back — keep looking »