Simon

Visual Studio 2010 – Testing Tools Demo with WPF

2010-03-08T13:23:00.002+09:00

I have been “testing” the new Testing Tools for Visual Studio 2010. This includes the new Lab Management and Test Manager. The Lab Management piece covers the managing of Virtual Environments and Machines for testing. The Test Manager is a GUI interface to Lab Management and a tool to manage test cases, bugs, and run tests.

In this blog entry, I want to show a demo of using the Testing Tools with a WPF application. I will show creating a test, running the test in a virtual environment, creating a bug, fixing the bug, building and deploying to the virtual environment, and verifying the bug fix.

OK, here we go.

0. Introduction of Test Environment.

The screen print above is from Test Manager showing the Lab Environment. I have created a Virtual Environment called “Xiptor Demo” and within the environment is one virtual machine, also named “Xiptor Demo”

The virtual machine (VM) is running Windows 7 with the test, lab, and build agents running. Also, Test Manager is installed on the VM.

1. Create Test Case

Now, in Test Manager, I create a Test Plan and add a new Test Suite as seen in the left side of the UI. Then, I will click on “New” to create a new test case.

I enter the Title and some steps to run the test case. Then I save the test case to TFS.

2. Run Test Case from Virtual Machine

In Test Manager, I want to bring up the VM environment viewer to run the test case and start Test Manager. I will select the test case and run.

I will start the test from the Test Runner (on left side of Environment Viewer window) and execute the test steps. I will start the WPF application and specify the test step passed. Then, when I click on a button, the WPF application crashes. So, I create a screen print. Then, I create a bug. The Test Runner will collect all the data to include in the bug and show the New Bug Window. After entering a title for the Bug, I will save the bug information to TFS.

3. Fix Bug in Visual Studio 2010

In Visual Studio 2010 using Team Explorer, I look at the bugs and find the bug just created. Here you can the details of the bug and there are links to the screenshot, actions list, System Information, a video recording of the test session, and IntelliTrace information.

If you click on the IntelliTrace link, you can see the IntelliTrace information saved while running the test. Double clicking on the Exception Data will bring me to the line of code where the exception occurred.

Now, I go ahead and fix the bug. When I check-in the source, I associate to a work item, which is the bug created in Test Manager.

4. Queue New Build with deploy to Lab Environment

After making all of the changes, I queue a new Lab build. The lab build will re-build the solution. Then, it will deploy the new version of the application to the Virtual Machine. Some optional items are to create a snapshot or checkpoint of the VM after deploying the build and running tests in the VM.

5. Verify Bug Fix in VM

I go back to the VM through Test Manager’s Environment Viewer to verify the bug fix. This time, instead of clicking on “Run Test”, I click on “Verify Bugs”. I select the “Resolved” bug and verify. This will start the Test Runner and run the “linked” test case.

6. Pass Test Case and Close Bug

I go through the test case steps and verify the bug was fixed. If everything was successful, I go ahead and Pass the test case and close Test Runner. When I close Test Runner, a window pops up to close the bug. I can enter some comments and click “Save Changes”.

Conclusion

Here are the basic steps in executing a test case, filing a bug, fixing a bug, build and deploy, and verifying bug fix. You got to see some of the features with the new testing tools, such as IntelliTrace, Managing VM Test environments, integration to TFS and Visual Studio. I hope this gave you a good start into understanding the new testing tools. I will be blogging in the future more about Visual Studio 2010 Testing tools.

.NET for iPhone

2009-12-16T14:27:00.001+09:00

A way to create applications for Windows Mobile is using the .NET Compact Framework. You can use your experience with .NET applications and languages to create applications for a Windows Mobile phone. Albeit the .NET Compact Framework has a lot of limitations compared to the full framework for Windows. That is a long story for another day…

But what about developing applications for the iPhone? Until recently the only way to develop iPhone applications is through the iPhone SDK (http://developer.apple.com/iphone/) There you need to learn Xcode, which is Apple’s Development IDE.

Now, there is a product for .NET developers to create applications on the iPhone and to release them to the iPhone App Store. Monotouch (http://monotouch.net) is an IDE to develop applications but it uses the C# syntax.

The Monotouch is only available for a Mac. Monotouch does include interfaces to iPhone APIs, such as access to GPS, accelerometer, address book, etc. It also uses the Cocoa Touch (Apple’s UI Framework) so you will have access to the native iPhone controls such as Pickers, Sliders, etc.

Here is a good article about using Monotouch on InfoQ (http://www.infoq.com/articles/monotouch-introduction). Monotouch is expensive, but it is a full development environment with the language syntax C#-like. If you are familiar with C# and want to develop iPhone applications, this is probably the fastest way to do it. On the other hand, you can download the iPhone SDK and learn Xcode and the C syntax to create the iPhone applications.

Prism 4.0 and MEF

2009-12-11T10:14:00.002+09:00

http://blogs.msdn.com/dphill/archive/2009/12/09/prism-and-mef.aspx

Interesting blog article talking about the future of Prism and integrating with MEF. It also touches on points where Prism and MEF overlap.

Happy Holidays

2009-12-10T15:15:00.000+09:00

First post to my new blog. Since it is the holiday season, just would like to wish everyone a Merry Christmas and have a Happy Holidays. Be safe with your Holiday parties and if you are in Korea, don't drink too much soju.