Home/ Questions/Q 4118078
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T22:54:52+00:00

Recently I was doing a lot of development in Microsoft Surface application’s. I also

  • 0

Recently I was doing a lot of development in Microsoft Surface application’s. I also read something about how these applications can be tested.

Currently I’m using Unit tests (package Microsoft.VisualStudio.TestTools.UnitTesting) to test the low level functionality of single methods. The user interface I’m testing with the Surface Simulator API. For both approaches I always create a extra project in the same solution.

But I’m not really sure if this is really a good approach. Unit testing is more or less ok, but the tests for the user interface are more or less limited by clicking various things and checking if there is no error. Although this checking is not really done explicitly.

So I’m asking are there any other approaches to beneficially test a Surface application?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Here’s how it’s done on the Surface team: The Simulator APIs included in the Surface SDK will let you automate sending fake touch input to your app. Combine that with WPF’s “Automation Peers” in order to automate validation that your UI is doing the right thing. For Surface controls that are derived from standard WPF controls, you can use the AutomationPeer classes that come with WPF. For Surface-specific controls like ScatterView, the Surface SDK includes it’s own set of AutomationPeer classes.

    If you’re unfamiliar with automation peers (and most people are), here’s a good introductory blog post on the topic: http://miketwo.blogspot.com/2007/03/unit-testing-wpf-controls-with.html

    • 0