CThru Wiki & Documentation Rss Feed

Updated Wiki: SilverUnit examples

RoyOsherove — Thu, 23 Sep 2010 16:36:36 GMT

SilverUnit

Download: Examples of tests using SilverUnit at: http://download.typemock.com/SilverUnitExamples.604.zip
Getting a SilverUnit project up and running
SilverUnit sits on top of Typemock Isolator's Open-AOP hooks. (Isolator is a commercial unit testing tool).
see also: Understanding the SilverUnit source code
see also: What is CThru: http://cthru.codeplex.com

Things to notice in the examples:

Tests can be run with the regular NUnit or MS Test tools. No need for specialized Silverlight-based compilation.
Objects under test can still be part of a Silverlight Assembly (in the examples, these are the Silverlight Toolkit Controls)
We simply "new" up objects under test. But the tests can be run in the regular CLR runtime, not in silverlight.
Tests do not run in the browser - they are fully in memory
Tests do no invoke the silverlight runtime, due to the use of the "SilverlightUnitTest" attribute

In C#

 [Test,SilverlightUnitTest]
 public void SetProperty()
 {
            var box = new AutoCompleteBox();
            box.MinimumPrefixLength = -3;
            int length =  (int) box.MinimumPrefixLength;
            Assert.AreEqual(-1, length);
  }


[Test,SilverlightUnitTest]
public void SetChildTemplate()
{

   //arrange
   var box = new AutoCompleteBox();

    //injecting our child controls into the parent control without needing XAML
    SilverUnit.SetTemplateChild(box, "Text", new TextBox());
    SilverUnit.SetTemplateChild(box, "Popup", new Popup()); 
    SilverUnit.SetTemplateChild(box, "SelectionAdapter", new ListBox());
    SilverUnit.SetTemplateChild(box, "DropDownToggle", new ToggleButton());

     //act
     box.OnApplyTemplate(); //full control of when to call OnApplyTemplate


      //assert      
      SilverUnit.Assert.VisualStatedWasChangedTo("Normal",box,false);   //special SilverUnit Assert to check moving to a Visual State
        }

In VB.NET

   //it's easy to trigger control events on any control using special extension methods
 <SilverlightUnitTest(), Test()> _
    Public Sub SetTextBox_SetTextOnTextBox_ACBoxIsUpdated()
        Dim txt As TextBox = New TextBox()
        Dim box As AutoCompleteBox = New AutoCompleteBox()
        txt.SelectionStart = 0
        txt.SelectionLength = 0
        txt.IsEnabled = True
        txt.Focus()

        box.TextBox = txt
        txt.Text = "a"
        txt.FireEvent(Events.TextChanged, Me, FakeInstance(Of TextChangedEventArgs))    //here we also are able to send in fake event args

        Assert.AreEqual("a", box.Text)
        Assert.AreEqual(box.Text, txt.Text)

    End Sub

Updated Wiki: SilverUnit examples

RoyOsherove — Thu, 23 Sep 2010 16:36:22 GMT

SilverUnit

Download: Examples of tests using SilverUnit at: http://download.typemock.com/SilverUnitExamples.604.zip
Getting a SilverUnit project up and running
SilverUnit sits on top of Typemock Isolator's Open-AOP hooks. (Isolator is a commercial unit testing tool).
see also: Understanding the SilverUnit source code
see also: What is CThru: http://cthru.codeplex.com

Things to notice in the examples:

Tests can be run with the regular NUnit or MS Test tools. No need for specialized Silverlight-based compilation.
Objects under test can still be part of a Silverlight Assembly (in the examples, these are the Silverlight Toolkit Controls)
We simply "new" up objects under test. But the tests can be run in the regular CLR runtime, not in silverlight.
Tests do not run in the browser - they are fully in memory
Tests do no invoke the silverlight runtime, due to the use of the "SilverlightUnitTest" attribute

In C#

 [Test,SilverlightUnitTest]
 public void SetProperty()
 {
            var box = new AutoCompleteBox();
            box.MinimumPrefixLength = -3;
            int length =  (int) box.MinimumPrefixLength;
            Assert.AreEqual(-1, length);
  }


[Test,SilverlightUnitTest]
public void SetChildTemplate()
{

   //arrange
   var box = new AutoCompleteBox();

    //injecting our child controls into the parent control without needing XAML
    SilverUnit.SetTemplateChild(box, "Text", new TextBox());
    SilverUnit.SetTemplateChild(box, "Popup", new Popup()); 
    SilverUnit.SetTemplateChild(box, "SelectionAdapter", new ListBox());
    SilverUnit.SetTemplateChild(box, "DropDownToggle", new ToggleButton());

     //act
     box.OnApplyTemplate(); //full control of when to call OnApplyTemplate


      //assert      
      SilverUnit.Assert.VisualStatedWasChangedTo("Normal",box,false);   //special SilverUnit Assert to check moving to a Visual State
        }

In VB.NET

   //it's easy to trigger control events on any control using special extension methods
 <SilverlightUnitTest(), Test()> _
    Public Sub SetTextBox_SetTextOnTextBox_ACBoxIsUpdated()
        Dim txt As TextBox = New TextBox()
        Dim box As AutoCompleteBox = New AutoCompleteBox()
        txt.SelectionStart = 0
        txt.SelectionLength = 0
        txt.IsEnabled = True
        txt.Focus()

        box.TextBox = txt
        txt.Text = "a"
        txt.FireEvent(Events.TextChanged, Me, FakeInstance(Of TextChangedEventArgs))    //here we also are able to send in fake event args

        Assert.AreEqual("a", box.Text)
        Assert.AreEqual(box.Text, txt.Text)

    End Sub

Updated Wiki: SilverUnit examples

RoyOsherove — Thu, 23 Sep 2010 16:36:12 GMT

SilverUnit

Download: Examples of tests using SilverUnit at: http://download.typemock.com/SilverUnitExamples.604.zip
Getting a SilverUnit project up and running
SilverUnit sits on top of Typemock Isolator's Open-AOP hooks. (Isolator is a commercial unit testing tool).
see also: Understanding the SilverUnit source code
see also: What is CThru: http://cthru.codeplex.com

Things to notice in the examples:

Tests can be run with the regular NUnit or MS Test tools. No need for specialized Silverlight-based compilation.
Objects under test can still be part of a Silverlight Assembly (in the examples, these are the Silverlight Toolkit Controls)
We simply "new" up objects under test. But the tests can be run in the regular CLR runtime, not in silverlight.
Tests do not run in the browser - they are fully in memory
Tests do no invoke the silverlight runtime, due to the use of the "SilverlightUnitTest" attribute

In C#

 [Test,SilverlightUnitTest]
 public void SetProperty()
 {
            var box = new AutoCompleteBox();
            box.MinimumPrefixLength = -3;
            int length =  (int) box.MinimumPrefixLength;
            Assert.AreEqual(-1, length);
  }


[Test,SilverlightUnitTest]
public void SetChildTemplate()
{

   //arrange
   var box = new AutoCompleteBox();

    //injecting our child controls into the parent control without needing XAML
    SilverUnit.SetTemplateChild(box, "Text", new TextBox());
    SilverUnit.SetTemplateChild(box, "Popup", new Popup()); 
    SilverUnit.SetTemplateChild(box, "SelectionAdapter", new ListBox());
    SilverUnit.SetTemplateChild(box, "DropDownToggle", new ToggleButton());

     //act
     box.OnApplyTemplate(); //full control of when to call OnApplyTemplate


      //assert      
      SilverUnit.Assert.VisualStatedWasChangedTo("Normal",box,false);   //special SilverUnit Assert to check moving to a Visual State
        }

In VB.NET

   //it's easy to trigger control events on any control using special extension methods
 <SilverlightUnitTest(), Test()> _
    Public Sub SetTextBox_SetTextOnTextBox_ACBoxIsUpdated()
        Dim txt As TextBox = New TextBox()
        Dim box As AutoCompleteBox = New AutoCompleteBox()
        txt.SelectionStart = 0
        txt.SelectionLength = 0
        txt.IsEnabled = True
        txt.Focus()

        box.TextBox = txt
        txt.Text = "a"
        txt.FireEvent(Events.TextChanged, Me, FakeInstance(Of TextChangedEventArgs))    //here we also are able to send in fake event args

        Assert.AreEqual("a", box.Text)
        Assert.AreEqual(box.Text, txt.Text)

    End Sub

Updated Wiki: SilverUnit examples

RoyOsherove — Thu, 23 Sep 2010 16:35:54 GMT

SilverUnit

Download: Examples of tests using SilverUnit at: http://download.typemock.com/SilverUnitExamples.604.zip
Getting a SilverUnit project up and running
SilverUnit sits on top of Typemock Isolator's Open-AOP hooks. (Isolator is a commercial unit testing tool).
see also: Understanding the SilverUnit source code
see also: What is CThru:http://cthru.codeplex.com/

Things to notice in the examples:

Tests can be run with the regular NUnit or MS Test tools. No need for specialized Silverlight-based compilation.
Objects under test can still be part of a Silverlight Assembly (in the examples, these are the Silverlight Toolkit Controls)
We simply "new" up objects under test. But the tests can be run in the regular CLR runtime, not in silverlight.
Tests do not run in the browser - they are fully in memory
Tests do no invoke the silverlight runtime, due to the use of the "SilverlightUnitTest" attribute

In C#

 [Test,SilverlightUnitTest]
 public void SetProperty()
 {
            var box = new AutoCompleteBox();
            box.MinimumPrefixLength = -3;
            int length =  (int) box.MinimumPrefixLength;
            Assert.AreEqual(-1, length);
  }


[Test,SilverlightUnitTest]
public void SetChildTemplate()
{

   //arrange
   var box = new AutoCompleteBox();

    //injecting our child controls into the parent control without needing XAML
    SilverUnit.SetTemplateChild(box, "Text", new TextBox());
    SilverUnit.SetTemplateChild(box, "Popup", new Popup()); 
    SilverUnit.SetTemplateChild(box, "SelectionAdapter", new ListBox());
    SilverUnit.SetTemplateChild(box, "DropDownToggle", new ToggleButton());

     //act
     box.OnApplyTemplate(); //full control of when to call OnApplyTemplate


      //assert      
      SilverUnit.Assert.VisualStatedWasChangedTo("Normal",box,false);   //special SilverUnit Assert to check moving to a Visual State
        }

In VB.NET

   //it's easy to trigger control events on any control using special extension methods
 <SilverlightUnitTest(), Test()> _
    Public Sub SetTextBox_SetTextOnTextBox_ACBoxIsUpdated()
        Dim txt As TextBox = New TextBox()
        Dim box As AutoCompleteBox = New AutoCompleteBox()
        txt.SelectionStart = 0
        txt.SelectionLength = 0
        txt.IsEnabled = True
        txt.Focus()

        box.TextBox = txt
        txt.Text = "a"
        txt.FireEvent(Events.TextChanged, Me, FakeInstance(Of TextChangedEventArgs))    //here we also are able to send in fake event args

        Assert.AreEqual("a", box.Text)
        Assert.AreEqual(box.Text, txt.Text)

    End Sub

Updated Wiki: SilverUnit examples

RoyOsherove — Thu, 23 Sep 2010 16:34:27 GMT

SilverUnit

Download: Examples of tests using SilverUnit at: http://download.typemock.com/SilverUnitExamples.604.zip
Getting a SilverUnit project up and running
SilverUnit sits on top of Typemock Isolator's Open-AOP hooks. (Isolator is a commercial unit testing tool).
see also: Understanding the SilverUnit source code

Things to notice in the examples:

Tests can be run with the regular NUnit or MS Test tools. No need for specialized Silverlight-based compilation.
Objects under test can still be part of a Silverlight Assembly (in the examples, these are the Silverlight Toolkit Controls)
We simply "new" up objects under test. But the tests can be run in the regular CLR runtime, not in silverlight.
Tests do not run in the browser - they are fully in memory
Tests do no invoke the silverlight runtime, due to the use of the "SilverlightUnitTest" attribute

In C#

 [Test,SilverlightUnitTest]
 public void SetProperty()
 {
            var box = new AutoCompleteBox();
            box.MinimumPrefixLength = -3;
            int length =  (int) box.MinimumPrefixLength;
            Assert.AreEqual(-1, length);
  }


[Test,SilverlightUnitTest]
public void SetChildTemplate()
{

   //arrange
   var box = new AutoCompleteBox();

    //injecting our child controls into the parent control without needing XAML
    SilverUnit.SetTemplateChild(box, "Text", new TextBox());
    SilverUnit.SetTemplateChild(box, "Popup", new Popup()); 
    SilverUnit.SetTemplateChild(box, "SelectionAdapter", new ListBox());
    SilverUnit.SetTemplateChild(box, "DropDownToggle", new ToggleButton());

     //act
     box.OnApplyTemplate(); //full control of when to call OnApplyTemplate


      //assert      
      SilverUnit.Assert.VisualStatedWasChangedTo("Normal",box,false);   //special SilverUnit Assert to check moving to a Visual State
        }

In VB.NET

   //it's easy to trigger control events on any control using special extension methods
 <SilverlightUnitTest(), Test()> _
    Public Sub SetTextBox_SetTextOnTextBox_ACBoxIsUpdated()
        Dim txt As TextBox = New TextBox()
        Dim box As AutoCompleteBox = New AutoCompleteBox()
        txt.SelectionStart = 0
        txt.SelectionLength = 0
        txt.IsEnabled = True
        txt.Focus()

        box.TextBox = txt
        txt.Text = "a"
        txt.FireEvent(Events.TextChanged, Me, FakeInstance(Of TextChangedEventArgs))    //here we also are able to send in fake event args

        Assert.AreEqual("a", box.Text)
        Assert.AreEqual(box.Text, txt.Text)

    End Sub

Updated Wiki: SilverUnit examples

RoyOsherove — Thu, 23 Sep 2010 16:34:00 GMT

SilverUnit

Download: Examples of tests using SilverUnit at: urlhttp://download.typemock.com/SilverUnitExamples.604.zip
Getting a SilverUnit project up and running
SilverUnit sits on top of Typemock Isolator's Open-AOP hooks. (Isolator is a commercial unit testing tool).
see also: Understanding the SilverUnit source code

Things to notice in the examples:

Tests can be run with the regular NUnit or MS Test tools. No need for specialized Silverlight-based compilation.
Objects under test can still be part of a Silverlight Assembly (in the examples, these are the Silverlight Toolkit Controls)
We simply "new" up objects under test. But the tests can be run in the regular CLR runtime, not in silverlight.
Tests do not run in the browser - they are fully in memory
Tests do no invoke the silverlight runtime, due to the use of the "SilverlightUnitTest" attribute

In C#

 [Test,SilverlightUnitTest]
 public void SetProperty()
 {
            var box = new AutoCompleteBox();
            box.MinimumPrefixLength = -3;
            int length =  (int) box.MinimumPrefixLength;
            Assert.AreEqual(-1, length);
  }


[Test,SilverlightUnitTest]
public void SetChildTemplate()
{

   //arrange
   var box = new AutoCompleteBox();

    //injecting our child controls into the parent control without needing XAML
    SilverUnit.SetTemplateChild(box, "Text", new TextBox());
    SilverUnit.SetTemplateChild(box, "Popup", new Popup()); 
    SilverUnit.SetTemplateChild(box, "SelectionAdapter", new ListBox());
    SilverUnit.SetTemplateChild(box, "DropDownToggle", new ToggleButton());

     //act
     box.OnApplyTemplate(); //full control of when to call OnApplyTemplate


      //assert      
      SilverUnit.Assert.VisualStatedWasChangedTo("Normal",box,false);   //special SilverUnit Assert to check moving to a Visual State
        }

In VB.NET

   //it's easy to trigger control events on any control using special extension methods
 <SilverlightUnitTest(), Test()> _
    Public Sub SetTextBox_SetTextOnTextBox_ACBoxIsUpdated()
        Dim txt As TextBox = New TextBox()
        Dim box As AutoCompleteBox = New AutoCompleteBox()
        txt.SelectionStart = 0
        txt.SelectionLength = 0
        txt.IsEnabled = True
        txt.Focus()

        box.TextBox = txt
        txt.Text = "a"
        txt.FireEvent(Events.TextChanged, Me, FakeInstance(Of TextChangedEventArgs))    //here we also are able to send in fake event args

        Assert.AreEqual("a", box.Text)
        Assert.AreEqual(box.Text, txt.Text)

    End Sub

Updated Wiki: SilverUnit examples

RoyOsherove — Thu, 23 Sep 2010 16:33:04 GMT

SilverUnit

Download: Examples of tests using SilverUnit[http://download.typemock.com/SilverUnitExamples.604.zip]
Getting a SilverUnit project up and running
SilverUnit sits on top of Typemock Isolator's Open-AOP hooks. (Isolator is a commercial unit testing tool).
see also: Understanding the SilverUnit source code

Things to notice in the examples:

Tests can be run with the regular NUnit or MS Test tools. No need for specialized Silverlight-based compilation.
Objects under test can still be part of a Silverlight Assembly (in the examples, these are the Silverlight Toolkit Controls)
We simply "new" up objects under test. But the tests can be run in the regular CLR runtime, not in silverlight.
Tests do not run in the browser - they are fully in memory
Tests do no invoke the silverlight runtime, due to the use of the "SilverlightUnitTest" attribute

In C#

 [Test,SilverlightUnitTest]
 public void SetProperty()
 {
            var box = new AutoCompleteBox();
            box.MinimumPrefixLength = -3;
            int length =  (int) box.MinimumPrefixLength;
            Assert.AreEqual(-1, length);
  }


[Test,SilverlightUnitTest]
public void SetChildTemplate()
{

   //arrange
   var box = new AutoCompleteBox();

    //injecting our child controls into the parent control without needing XAML
    SilverUnit.SetTemplateChild(box, "Text", new TextBox());
    SilverUnit.SetTemplateChild(box, "Popup", new Popup()); 
    SilverUnit.SetTemplateChild(box, "SelectionAdapter", new ListBox());
    SilverUnit.SetTemplateChild(box, "DropDownToggle", new ToggleButton());

     //act
     box.OnApplyTemplate(); //full control of when to call OnApplyTemplate


      //assert      
      SilverUnit.Assert.VisualStatedWasChangedTo("Normal",box,false);   //special SilverUnit Assert to check moving to a Visual State
        }

In VB.NET

   //it's easy to trigger control events on any control using special extension methods
 <SilverlightUnitTest(), Test()> _
    Public Sub SetTextBox_SetTextOnTextBox_ACBoxIsUpdated()
        Dim txt As TextBox = New TextBox()
        Dim box As AutoCompleteBox = New AutoCompleteBox()
        txt.SelectionStart = 0
        txt.SelectionLength = 0
        txt.IsEnabled = True
        txt.Focus()

        box.TextBox = txt
        txt.Text = "a"
        txt.FireEvent(Events.TextChanged, Me, FakeInstance(Of TextChangedEventArgs))    //here we also are able to send in fake event args

        Assert.AreEqual("a", box.Text)
        Assert.AreEqual(box.Text, txt.Text)

    End Sub

Updated Wiki: SilverUnit examples

RoyOsherove — Thu, 10 Dec 2009 21:25:16 GMT

SilverUnit

Getting a SilverUnit project up and running
SilverUnit sits on top of Typemock Isolator's Open-AOP hooks. (Isolator is a commercial unit testing tool).
see also: Understanding the SilverUnit source code

Things to notice in the examples:

Tests can be run with the regular NUnit or MS Test tools. No need for specialized Silverlight-based compilation.
Objects under test can still be part of a Silverlight Assembly (in the examples, these are the Silverlight Toolkit Controls)
We simply "new" up objects under test. But the tests can be run in the regular CLR runtime, not in silverlight.
Tests do not run in the browser - they are fully in memory
Tests do no invoke the silverlight runtime, due to the use of the "SilverlightUnitTest" attribute

In C#

 [Test,SilverlightUnitTest]
 public void SetProperty()
 {
            var box = new AutoCompleteBox();
            box.MinimumPrefixLength = -3;
            int length =  (int) box.MinimumPrefixLength;
            Assert.AreEqual(-1, length);
  }


[Test,SilverlightUnitTest]
public void SetChildTemplate()
{

   //arrange
   var box = new AutoCompleteBox();

    //injecting our child controls into the parent control without needing XAML
    SilverUnit.SetTemplateChild(box, "Text", new TextBox());
    SilverUnit.SetTemplateChild(box, "Popup", new Popup()); 
    SilverUnit.SetTemplateChild(box, "SelectionAdapter", new ListBox());
    SilverUnit.SetTemplateChild(box, "DropDownToggle", new ToggleButton());

     //act
     box.OnApplyTemplate(); //full control of when to call OnApplyTemplate


      //assert      
      SilverUnit.Assert.VisualStatedWasChangedTo("Normal",box,false);   //special SilverUnit Assert to check moving to a Visual State
        }

In VB.NET

   //it's easy to trigger control events on any control using special extension methods
 <SilverlightUnitTest(), Test()> _
    Public Sub SetTextBox_SetTextOnTextBox_ACBoxIsUpdated()
        Dim txt As TextBox = New TextBox()
        Dim box As AutoCompleteBox = New AutoCompleteBox()
        txt.SelectionStart = 0
        txt.SelectionLength = 0
        txt.IsEnabled = True
        txt.Focus()

        box.TextBox = txt
        txt.Text = "a"
        txt.FireEvent(Events.TextChanged, Me, FakeInstance(Of TextChangedEventArgs))    //here we also are able to send in fake event args

        Assert.AreEqual("a", box.Text)
        Assert.AreEqual(box.Text, txt.Text)

    End Sub

Updated Wiki: SilverUnit examples

RoyOsherove — Thu, 10 Dec 2009 21:19:26 GMT

SilverUnit

Getting a SilverUnit project up and running
SilverUnit sits on top of Typemock Isolator's Open-AOP hooks. (Isolator is a commercial unit testing tool).
see also: Understanding the SilverUnit source code

Things to notice in the examples:

Tests can be run with the regular NUnit or MS Test tools. No need for specialized Silverlight-based compilation.
Objects under test can still be part of a Silverlight Assembly (in the examples, these are the Silverlight Toolkit Controls)
We simply "new" up objects under test. But the tests can be run in the regular CLR runtime, not in silverlight.
Tests do not run in the browser - they are fully in memory
Tests do no invoke the silverlight runtime, due to the use of the "SilverlightUnitTest" attribute

In C#

 [Test,SilverlightUnitTest]
 public void SetProperty()
 {
            var box = new AutoCompleteBox();
            box.MinimumPrefixLength = -3;
            int length =  (int) box.MinimumPrefixLength;
            Assert.AreEqual(-1, length);
  }


        [Test,SilverlightUnitTest]
        public void SetChildTemplate()
        {
            var box = new AutoCompleteBox();

            //injecting our child controls into the parent control without needing XAML
            SilverUnit.SetTemplateChild(box, "Text", new TextBox());
            SilverUnit.SetTemplateChild(box, "Popup", new Popup()); 
            SilverUnit.SetTemplateChild(box, "SelectionAdapter", new ListBox());
            SilverUnit.SetTemplateChild(box, "DropDownToggle", new ToggleButton());

            box.OnApplyTemplate(); //full control of when to call OnApplyTemplate


            SilverUnit.Assert.VisualStatedWasChangedTo("Normal",box,false);   //special SilverUnit Assert to check moving to a Visual State
        }

New Comment on "Getting a SilverUnit project up and running"

martinording — Thu, 30 Jul 2009 15:04:37 GMT

I created a new silverunit test project using the template, having SL 3.0 as the framework. I right click on ControlTests1.cs and choose Run Test(s). I get: The target type doesn't contain tests from a known test framework or a 'Main' method. The same thing happens if I go to the submenu and click Run with Debugger/Coverage/TypeMock. I can run the examples (framework 3.5) from TypeMock just fine. Any ideas?

Updated Wiki: Getting a SilverUnit project up and running

RoyOsherove — Sun, 24 May 2009 10:38:29 GMT

Setting up a SilverUnit project

To start using SilverUnit you will need:

The latest version of Typemock Isolator installed on the local machine (currently it is 5.3)
The latest version of the SilverUnit dlls (currently 0.4) : CThru.dll and CThru.Silverlight.dll that were compiled against the latest version of Isolator.
A silverlight class library or executable project that you'd like to test (compiled or as source)
Visual Studio Express or above
NUnit, MbUnit or MSTest

Using the SilverUnit Project Template

The simplest solution to start writing a test would be to download the SilverUnit project template for visual studio from the latest release.
double click on the downloaded .vsi file and visual studio will create a new project type under "silverlight" for you. More details here
if you somehow are not able to do this, then follow the instructions below.

Follow these steps to create a project Manually

NOTE: only use these instructions if you are not going to use the project template installer (in the paragraph above).
Create an empty solution in visual studio
Add the Silverlight project that you'd like to test to the solution projects
Create a new standard (not Silverlight!) class library project in C# or VB.NET (this is where you will write your tests)
Add a reference to NUnit or MSTest or MbUnit so you can write tests with it.
right click on the test project (the standard class library) and Add a reference to the silverlight project that you'd like to test
In the test project, remove references to System.core, system.xml
in the test project, add references to the silverlight versions of system.core, system.xml and the other system.* dlls from silverlight.
Continue changing the references until everthing compiles successfully (If you have resharper it might think that there are problems, but as long as compilation passes you're OK.

Add references for SilverUnit

Add references to Typemock.dll (from the ".NET" tab) as well as to the CThru.dll and CThru.Silverlight.dll

You should now be able to write a test that looks somewhat like this:

[TestMethod]
[SilverlightUnitTest]  // <----- where the magic happens
public void SomeTestAgainstSilverlight()
{
//code against silverlight here
}

How to know SilverUnit is working

When SilverUnit is running the first test, you should see in the output console a sentence similar to the following:
"Loading isolation aspects..."
If you see nothing that looks like this before the first test is running it means that something is wrong and SilverUnit is not really isolating you from the Silverlight runtime objects (you'll also get nasty exceptions relating to DependencyObject based classes)

It's not working. What do I do?

make sure you have the latest version of Typemock Isolator running and enabled in the process that is running the test. If it's not running inside visual studio you may need to run that process using TMockRunner.exe which is part of Typemock's Installation
Make sure you have the latest version of the compiled CThru and SilverUnit binaries (0.4 as of writing). These are compiled against the core typemock.dll with version 5.3. it will not work otherwise.
if you are getting "could not load file or dependencies" stuff, it most likely is a reference problem. remove all unneeded references from the test project as long as it still compiles. Also add the silverlight versions of those dlls if they are reported as not found, as references to the test project.

I'm getting a nasty exception from "JoltHelper" and none of the above is relevant

Make sure that you are not creating instances of your controls inside a SetUp or TestInitialize method. Create instances of objects inheriting from DependencyObject only from inside the test, because that is when the SilverUnit engine begins to work. For now this should be the practice. Do not use "new" on things inheriting from DependencyObject in a setup method.
Examples:
Good:

private MyControl control;
[Test,SilverlightUnitTest]
public void SomeTest()
{
control = new MyControl();  //<---- *this is OK*
myControl.DoSomething();//
}

Not good:

private MyControl control;
[SetUp]
public void Setup()
{
control = new MyControl();  //<---- *big no no*
}
[Test,SilverlightUnitTest]
public void SomeTest()
{
myControl.DoSomething();//
}

Can I use SilverUnit inside a project that uses the Silverlight test framework from Microsoft?

You can't. Silverunit is based on the regular CLR runtime, and the MS test framework is compiled against the silverlight runtime. You can't use both of them on the same project (and you shouldn't need to). Have one project which holds unit tests and uses SilverUnit, and another project that holds Integration Tests and uses the MS test framework.

Does SilverUnit support Silverlight 3.0?

Not officially. It has not been tested with it yet. There is a very high chance that tests already written against silverlight 2.0 should just work if the code under test is compiled into Silverlight 3.0.

Updated Wiki: Getting a SilverUnit project up and running

RoyOsherove — Sat, 23 May 2009 19:55:50 GMT

Setting up a SilverUnit project

To start using SilverUnit you will need:

The latest version of Typemock Isolator installed on the local machine (currently it is 5.3)
The latest version of the SilverUnit dlls (currently 0.4) : CThru.dll and CThru.Silverlight.dll that were compiled against the latest version of Isolator.
A silverlight class library or executable project that you'd like to test (compiled or as source)
Visual Studio Express or above
NUnit, MbUnit or MSTest

Using the SilverUnit Project Template

The simplest solution to start writing a test would be to download the SilverUnit project template for visual studio from the latest release.
double click on the downloaded .vsi file and visual studio will create a new project type under "silverlight" for you. More details here
if you somehow are not able to do this, then follow the instructions below.

Follow these steps to create a project Manually

NOTE: only use these instructions if you are not going to use the project template installer (in the paragraph above).
Create an empty solution in visual studio
Add the Silverlight project that you'd like to test to the solution projects
Create a new standard (not Silverlight!) class library project in C# or VB.NET (this is where you will write your tests)
Add a reference to NUnit or MSTest or MbUnit so you can write tests with it.
right click on the test project (the standard class library) and Add a reference to the silverlight project that you'd like to test
In the test project, remove references to System.core, system.xml
in the test project, add references to the silverlight versions of system.core, system.xml and the other system.* dlls from silverlight.
Continue changing the references until everthing compiles successfully (If you have resharper it might think that there are problems, but as long as compilation passes you're OK.

Add references for SilverUnit

Add references to Typemock.dll (from the ".NET" tab) as well as to the CThru.dll and CThru.Silverlight.dll

You should now be able to write a test that looks somewhat like this:

[TestMethod]
[SilverlightUnitTest]  // <----- where the magic happens
public void SomeTestAgainstSilverlight()
{
//code against silverlight here
}

How to know SilverUnit is working

It's not working. What do I do?

make sure you have the latest version of Typemock Isolator running and enabled in the process that is running the test. If it's not running inside visual studio you may need to run that process using TMockRunner.exe which is part of Typemock's Installation
Make sure you have the latest version of the compiled CThru and SilverUnit binaries (0.4 as of writing). These are compiled against the core typemock.dll with version 5.3. it will not work otherwise.
if you are getting "could not load file or dependencies" stuff, it most likely is a reference problem. remove all unneeded references from the test project as long as it still compiles. Also add the silverlight versions of those dlls if they are reported as not found, as references to the test project.

I'm getting a nasty exception from "JoltHelper" and none of the above is relevant

private MyControl control;
[Test,SilverlightUnitTest]
public void SomeTest()
{
control = new MyControl();  //<---- *this is OK*
myControl.DoSomething();//
}

Not good:

private MyControl control;
[SetUp]
public void Setup()
{
control = new MyControl();  //<---- *big no no*
}
[Test,SilverlightUnitTest]
public void SomeTest()
{
myControl.DoSomething();//
}

Can I use SilverUnit inside a project that uses the Silverlight test framework from Microsoft?

Does SilverUnit support Silverlight 3.0?

Updated Wiki: Getting a SilverUnit project up and running

RoyOsherove — Sat, 23 May 2009 19:55:02 GMT

Setting up a SilverUnit project

To start using SilverUnit you will need:

The latest version of Typemock Isolator installed on the local machine (currently it is 5.3)
The latest version of the SilverUnit dlls (currently 0.4) : CThru.dll and CThru.Silverlight.dll that were compiled against the latest version of Isolator.
A silverlight class library or executable project that you'd like to test (compiled or as source)
Visual Studio Express or above
NUnit, MbUnit or MSTest

Using the SilverUnit Project Template

The simplest solution to start writing a test would be to download the SilverUnit project template for visual studio from the latest release.
double click on the downloaded .vsi file and visual studio will create a new project type under "silverlight" for you. More details here
if you somehow are not able to do this, then follow the instructions below.

Follow these steps to create a project

NOTE: only use these instructions if you are not going to use the project template installer (in the paragraph above).
Create an empty solution in visual studio
Add the Silverlight project that you'd like to test to the solution projects
Create a new standard (not Silverlight!) class library project in C# or VB.NET (this is where you will write your tests)
Add a reference to NUnit or MSTest or MbUnit so you can write tests with it.
right click on the test project (the standard class library) and Add a reference to the silverlight project that you'd like to test
In the test project, remove references to System.core, system.xml
in the test project, add references to the silverlight versions of system.core, system.xml and the other system.* dlls from silverlight.
Continue changing the references until everthing compiles successfully (If you have resharper it might think that there are problems, but as long as compilation passes you're OK.

Add references for SilverUnit

Add references to Typemock.dll (from the ".NET" tab) as well as to the CThru.dll and CThru.Silverlight.dll

You should now be able to write a test that looks somewhat like this:

[TestMethod]
[SilverlightUnitTest]  // <----- where the magic happens
public void SomeTestAgainstSilverlight()
{
//code against silverlight here
}

How to know SilverUnit is working

It's not working. What do I do?

make sure you have the latest version of Typemock Isolator running and enabled in the process that is running the test. If it's not running inside visual studio you may need to run that process using TMockRunner.exe which is part of Typemock's Installation
Make sure you have the latest version of the compiled CThru and SilverUnit binaries (0.4 as of writing). These are compiled against the core typemock.dll with version 5.3. it will not work otherwise.
if you are getting "could not load file or dependencies" stuff, it most likely is a reference problem. remove all unneeded references from the test project as long as it still compiles. Also add the silverlight versions of those dlls if they are reported as not found, as references to the test project.

I'm getting a nasty exception from "JoltHelper" and none of the above is relevant

private MyControl control;
[Test,SilverlightUnitTest]
public void SomeTest()
{
control = new MyControl();  //<---- *this is OK*
myControl.DoSomething();//
}

Not good:

private MyControl control;
[SetUp]
public void Setup()
{
control = new MyControl();  //<---- *big no no*
}
[Test,SilverlightUnitTest]
public void SomeTest()
{
myControl.DoSomething();//
}

Can I use SilverUnit inside a project that uses the Silverlight test framework from Microsoft?

Does SilverUnit support Silverlight 3.0?

Updated Wiki: Getting a SilverUnit project up and running

RoyOsherove — Tue, 12 May 2009 00:29:21 GMT

Setting up a SilverUnit project

To start using SilverUnit you will need:

The latest version of Typemock Isolator installed on the local machine (currently it is 5.3)
The latest version of the SilverUnit dlls (currently 0.4) : CThru.dll and CThru.Silverlight.dll that were compiled against the latest version of Isolator.
A silverlight class library or executable project that you'd like to test (compiled or as source)
Visual Studio Express or above
NUnit, MbUnit or MSTest

Follow these steps to create a project

Create an empty solution in visual studio
Add the Silverlight project that you'd like to test to the solution projects
Create a new standard (not Silverlight!) class library project in C# or VB.NET (this is where you will write your tests)
Add a reference to NUnit or MSTest or MbUnit so you can write tests with it.
right click on the test project (the standard class library) and Add a reference to the silverlight project that you'd like to test
In the test project, remove references to System.core, system.xml
in the test project, add references to the silverlight versions of system.core, system.xml and the other system.* dlls from silverlight.
Continue changing the references until everthing compiles successfully (If you have resharper it might think that there are problems, but as long as compilation passes you're OK.

Add references for SilverUnit

Add references to Typemock.dll (from the ".NET" tab) as well as to the CThru.dll and CThru.Silverlight.dll

You should now be able to write a test that looks somewhat like this:

[TestMethod]
[SilverlightUnitTest]  // <----- where the magic happens
public void SomeTestAgainstSilverlight()
{
//code against silverlight here
}

How to know SilverUnit is working

It's not working. What do I do?

make sure you have the latest version of Typemock Isolator running and enabled in the process that is running the test. If it's not running inside visual studio you may need to run that process using TMockRunner.exe which is part of Typemock's Installation
Make sure you have the latest version of the compiled CThru and SilverUnit binaries (0.4 as of writing). These are compiled against the core typemock.dll with version 5.3. it will not work otherwise.
if you are getting "could not load file or dependencies" stuff, it most likely is a reference problem. remove all unneeded references from the test project as long as it still compiles. Also add the silverlight versions of those dlls if they are reported as not found, as references to the test project.

I'm getting a nasty exception from "JoltHelper" and none of the above is relevant

private MyControl control;
[Test,SilverlightUnitTest]
public void SomeTest()
{
control = new MyControl();  //<---- *this is OK*
myControl.DoSomething();//
}

Not good:

private MyControl control;
[SetUp]
public void Setup()
{
control = new MyControl();  //<---- *big no no*
}
[Test,SilverlightUnitTest]
public void SomeTest()
{
myControl.DoSomething();//
}

Can I use SilverUnit inside a project that uses the Silverlight test framework from Microsoft?

Does SilverUnit support Silverlight 3.0?

Updated Wiki: Getting a SilverUnit project up and running

RoyOsherove — Mon, 11 May 2009 23:26:01 GMT

Setting up a SilverUnit project

To start using SilverUnit you will need:

The latest version of Typemock Isolator installed on the local machine (currently it is 5.3)
The latest version of the SilverUnit dlls (currently 0.4) : CThru.dll and CThru.Silverlight.dll that were compiled against the latest version of Isolator.
A silverlight class library or executable project that you'd like to test (compiled or as source)
Visual Studio Express or above
NUnit, MbUnit or MSTest

Follow these steps to create a project (or alternatively use the NUnit-Silverlight template)

Create an empty solution in visual studio
Add the Silverlight project that you'd like to test to the solution projects
Create a new standard (not Silverlight!) class library project in C# or VB.NET (this is where you will write your tests)
Add a reference to NUnit or MSTest or MbUnit so you can write tests with it.
right click on the test project (the standard class library) and Add a reference to the silverlight project that you'd like to test
In the test project, remove references to System.core, system.xml
in the test project, add references to the silverlight versions of system.core, system.xml and the other system.* dlls from silverlight.
Continue changing the references until everthing compiles successfully (If you have resharper it might think that there are problems, but as long as compilation passes you're OK.

Add references for SilverUnit

Add references to Typemock.dll (from the ".NET" tab) as well as to the CThru.dll and CThru.Silverlight.dll

You should now be able to write a test that looks somewhat like this:

[TestMethod]
[SilverlightUnitTest]  // <----- where the magic happens
public void SomeTestAgainstSilverlight()
{
//code against silverlight here
}

How to know SilverUnit is working

It's not working. What do I do?

make sure you have the latest version of Typemock Isolator running and enabled in the process that is running the test. If it's not running inside visual studio you may need to run that process using TMockRunner.exe which is part of Typemock's Installation
Make sure you have the latest version of the compiled CThru and SilverUnit binaries (0.4 as of writing). These are compiled against the core typemock.dll with version 5.3. it will not work otherwise.
if you are getting "could not load file or dependencies" stuff, it most likely is a reference problem. remove all unneeded references from the test project as long as it still compiles. Also add the silverlight versions of those dlls if they are reported as not found, as references to the test project.

I'm getting a nasty exception from "JoltHelper" and none of the above is relevant

private MyControl control;
[Test,SilverlightUnitTest]
public void SomeTest()
{
control = new MyControl();  //<---- *this is OK*
myControl.DoSomething();//
}

Not good:

private MyControl control;
[SetUp]
public void Setup()
{
control = new MyControl();  //<---- *big no no*
}
[Test,SilverlightUnitTest]
public void SomeTest()
{
myControl.DoSomething();//
}

Can I use SilverUnit inside a project that uses the Silverlight test framework from Microsoft?

Does SilverUnit support Silverlight 3.0?

Updated Wiki: Getting a SilverUnit project up and running

RoyOsherove — Mon, 11 May 2009 23:25:05 GMT

Setting up a SilverUnit project

To start using SilverUnit you will need:

The latest version of Typemock Isolator installed on the local machine (currently it is 5.3)
The latest version of the SilverUnit dlls (currently 0.4) : CThru.dll and CThru.Silverlight.dll that were compiled against the latest version of Isolator.
A silverlight class library or executable project that you'd like to test (compiled or as source)
Visual Studio Express or above
NUnit, MbUnit or MSTest

Follow these steps to create a project (or alternatively use the NUnit-Silverlight template)

Create an empty solution in visual studio
Add the Silverlight project that you'd like to test to the solution projects
Create a new standard (not Silverlight!) class library project in C# or VB.NET (this is where you will write your tests)
Add a reference to NUnit or MSTest or MbUnit so you can write tests with it.
right click on the test project (the standard class library) and Add a reference to the silverlight project that you'd like to test
In the test project, remove references to System.core, system.xml
in the test project, add references to the silverlight versions of system.core, system.xml and the other system.* dlls from silverlight.
Continue changing the references until everthing compiles successfully (If you have resharper it might think that there are problems, but as long as compilation passes you're OK.
Add references to Typemock.dll (from the ".NET" tab) as well as to the CThru.dll and CThru.Silverlight.dll

You should now be able to write a test that looks somewhat like this:

[TestMethod]
[SilverlightUnitTest]  // <----- where the magic happens
public void SomeTestAgainstSilverlight()
{
//code against silverlight here
}

How to know SilverUnit is working

It's not working. What do I do?

make sure you have the latest version of Typemock Isolator running and enabled in the process that is running the test. If it's not running inside visual studio you may need to run that process using TMockRunner.exe which is part of Typemock's Installation
Make sure you have the latest version of the compiled CThru and SilverUnit binaries (0.4 as of writing). These are compiled against the core typemock.dll with version 5.3. it will not work otherwise.
if you are getting "could not load file or dependencies" stuff, it most likely is a reference problem. remove all unneeded references from the test project as long as it still compiles. Also add the silverlight versions of those dlls if they are reported as not found, as references to the test project.

I'm getting a nasty exception from "JoltHelper" and none of the above is relevant

private MyControl control;
[Test,SilverlightUnitTest]
public void SomeTest()
{
control = new MyControl();  //<---- *this is OK*
myControl.DoSomething();//
}

Not good:

private MyControl control;
[SetUp]
public void Setup()
{
control = new MyControl();  //<---- *big no no*
}
[Test,SilverlightUnitTest]
public void SomeTest()
{
myControl.DoSomething();//
}

Can I use SilverUnit inside a project that uses the Silverlight test framework from Microsoft?

Does SilverUnit support Silverlight 3.0?

New Comment on "Getting a SilverUnit project up and running"

chakrit — Sat, 09 May 2009 18:56:03 GMT

TypeMock Isolator is a total deal breaker... is it possible to use another mocking framework instead?

Updated Wiki: SilverUnit examples

RoyOsherove — Wed, 01 Apr 2009 20:22:40 GMT

SilverUnit

Getting a SilverUnit project up and running
SilverUnit sits on top of Typemock Isolator's Open-AOP hooks. (Isolator is a commercial unit testing tool).
see also: Understanding the SilverUnit source code

Things to notice in the examples:

Tests can be run with the regular NUnit or MS Test tools. No need for specialized Silverlight-based compilation.
Objects under test can still be part of a Silverlight Assembly (in the examples, these are the Silverlight Toolkit Controls)
We simply "new" up objects under test. But the tests can be run in the regular CLR runtime, not in silverlight.
Tests do not run in the browser - they are fully in memory
Tests do no invoke the silverlight runtime, due to the use of the "SilverlightUnitTest" attribute

In VB.NET:

This test sets dependency properties and checks what happens when an Invalid value is set on them.
The next one uses two controls with each other.

 <SilverlightUnitTest(), Test()> _
        Public Sub MinimumPrefixLength_SetToLessThanMinusOne_ResetsToMinusOne()
        Dim box As AutoCompleteBox = New AutoCompleteBox
        box.MinimumPrefixLength = -3
        Assert.AreEqual(-1, box.MinimumPrefixLength)
    End Sub
 
  <SilverlightUnitTest(), Test()> _
    Public Sub SetTextBox_SetTextOnCompleteBox_TextBGoxIsUpdatedWithCompleteBox()
        Dim txt As TextBox = New TextBox()
        Dim box As AutoCompleteBox = New AutoCompleteBox()
        txt.SelectionStart = 0
        txt.SelectionLength = 0
 
        box.TextBox = txt
        box.Text = "a"
        Assert.AreEqual("a", box.Text)
        Assert.AreEqual(box.Text, txt.Text)
 
    End Sub

In C#

 [Test,SilverlightUnitTest]
 public void SetProperty()
 {
            var box = new AutoCompleteBox();
            box.MinimumPrefixLength = -3;
            int length =  (int) box.MinimumPrefixLength;
            Assert.AreEqual(-1, length);
  }

Updated Wiki: Getting a SilverUnit project up and running

RoyOsherove — Wed, 01 Apr 2009 20:21:24 GMT

Setting up a SilverUnit project

To start using SilverUnit you will need:

The latest version of Typemock Isolator installed on the local machine (currently it is 5.3)
The latest version of the SilverUnit dlls (currently 0.4) : CThru.dll and CThru.Silverlight.dll that were compiled against the latest version of Isolator.
A silverlight class library or executable project that you'd like to test (compiled or as source)
Visual Studio Express or above
NUnit, MbUnit or MSTest

Follow these steps to create a project

Create an empty solution in visual studio
Add the Silverlight project that you'd like to test to the solution projects
Create a new standard (not Silverlight!) class library project in C# or VB.NET (this is where you will write your tests)
Add a reference to NUnit or MSTest or MbUnit so you can write tests with it.
right click on the test project (the standard class library) and Add a reference to the silverlight project that you'd like to test
In the test project, remove references to System.core, system.xml
in the test project, add references to the silverlight versions of system.core, system.xml and the other system.* dlls from silverlight.
Continue changing the references until everthing compiles successfully (If you have resharper it might think that there are problems, but as long as compilation passes you're OK.
Add references to Typemock.dll (from the ".NET" tab) as well as to the CThru.dll and CThru.Silverlight.dll

You should now be able to write a test that looks somewhat like this:

[TestMethod]
[SilverlightUnitTest]  // <----- where the magic happens
public void SomeTestAgainstSilverlight()
{
//code against silverlight here
}

How to know SilverUnit is working

It's not working. What do I do?

make sure you have the latest version of Typemock Isolator running and enabled in the process that is running the test. If it's not running inside visual studio you may need to run that process using TMockRunner.exe which is part of Typemock's Installation
Make sure you have the latest version of the compiled CThru and SilverUnit binaries (0.4 as of writing). These are compiled against the core typemock.dll with version 5.3. it will not work otherwise.
if you are getting "could not load file or dependencies" stuff, it most likely is a reference problem. remove all unneeded references from the test project as long as it still compiles. Also add the silverlight versions of those dlls if they are reported as not found, as references to the test project.

I'm getting a nasty exception from "JoltHelper" and none of the above is relevant

private MyControl control;
[Test,SilverlightUnitTest]
public void SomeTest()
{
control = new MyControl();  //<---- *this is OK*
myControl.DoSomething();//
}

Not good:

private MyControl control;
[SetUp]
public void Setup()
{
control = new MyControl();  //<---- *big no no*
}
[Test,SilverlightUnitTest]
public void SomeTest()
{
myControl.DoSomething();//
}

Can I use SilverUnit inside a project that uses the Silverlight test framework from Microsoft?

Does SilverUnit support Silverlight 3.0?

Updated Wiki: Getting a SilverUnit project up and running

RoyOsherove — Wed, 01 Apr 2009 20:17:38 GMT

Setting up a SilverUnit project

To start using SilverUnit you will need:

The latest version of Typemock Isolator installed on the local machine (currently it is 5.3)
The latest version of the SilverUnit dlls (currently 0.4) : CThru.dll and CThru.Silverlight.dll that were compiled against the latest version of Isolator.
A silverlight class library or executable project that you'd like to test (compiled or as source)
Visual Studio Express or above
NUnit, MbUnit or MSTest

Follow these steps to create a project

Create an empty solution in visual studio
Add the Silverlight project that you'd like to test to the solution projects
Create a new standard (not Silverlight!) class library project in C# or VB.NET (this is where you will write your tests)
Add a reference to NUnit or MSTest or MbUnit so you can write tests with it.
right click on the test project (the standard class library) and Add a reference to the silverlight project that you'd like to test
In the test project, remove references to System.core, system.xml
in the test project, add references to the silverlight versions of system.core, system.xml and the other system.* dlls from silverlight.
Continue changing the references until everthing compiles successfully (If you have resharper it might think that there are problems, but as long as compilation passes you're OK.
Add references to Typemock.dll (from the ".NET" tab) as well as to the CThru.dll and CThru.Silverlight.dll

You should now be able to write a test that looks somewhat like this:

[TestMethod]
[SilverlightUnitTest]
public void SomeTestAgainstSilverlight()
{
//code against silverlight here
}

How to know SilverUnit is working

It's not working. What do I do?

make sure you have the latest version of Typemock Isolator running and enabled in the process that is running the test. If it's not running inside visual studio you may need to run that process using TMockRunner.exe which is part of Typemock's Installation
Make sure you have the latest version of the compiled CThru and SilverUnit binaries (0.4 as of writing). These are compiled against the core typemock.dll with version 5.3. it will not work otherwise.
if you are getting "could not load file or dependencies" stuff, it most likely is a reference problem. remove all unneeded references from the test project as long as it still compiles. Also add the silverlight versions of those dlls if they are reported as not found, as references to the test project.

I'm getting a nasty exception from "JoltHelper" and none of the above is relevant

private MyControl control;
[Test,SilverlightUnitTest]
public void SomeTest()
{
control = new MyControl();  //<---- *this is OK*
myControl.DoSomething();//
}

Not good:

private MyControl control;
[SetUp]
public void Setup()
{
control = new MyControl();  //<---- *big no no*
}
[Test,SilverlightUnitTest]
public void SomeTest()
{
myControl.DoSomething();//
}