StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16547022
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
2013-05-14T15:28:49.523
CreationDate
2013-05-14T15:20:57.007
FavoriteCount
0
LastActivityDate
2013-05-14T15:38:25.543
LastEditDate
2013-05-14T15:38:25.543
LastEditorUserId
986451
OwnerUserId
986451
ParentId
308802
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Here is my definite guide to unit testing in Silverlight 5. This will guide to all the points you have to do, if you have no clue, where to start. This guide is about testing inside your project. You will not need a 2nd odr 3rd silverlight project to unit test. 0.) Close your Silverlight Project. 1.) Download the Silverlight 5 toolkit <a href="http://silverlight.codeplex.com/releases" rel="nofollow">here</a> and install it. 2.) Open your Windows Explorer, go to C: and then search for these two files: Microsoft.Silverlight.Testing.dll Microsoft.VisualStudio.QualityTools.UnitTesting.Silverlight.dll If you don't find them, something is wrong. 3.) Register these two DLLs in the GAC. For that do the follwing: Open the Visual Studio console as Administrator. Copy each of the statements and execute them in the console: gacutil /i "C:\Program Files\Microsoft SDKs\Silverlight\v5.0\Toolkit\dec11\Testing\Microsoft.Silverlight.Testing.dll" gacutil /i "C:\Program Files\Microsoft SDKs\Silverlight\v5.0\Toolkit\dec11\Testing\Microsoft.VisualStudio.QualityTools.UnitTesting.Silverlight.dll" Please keep in mind, that the paths to the DLLs could be different on your machine. Just type the correct path for your machine. 4. Open your Silverlight Project and add the two DLLs from above as a reference to Silverlight project. Not to your web project. 5. Add the following class to your project. It does not matter where you put it. I have an extra folder for my tests, but does'nt matter. <pre><code>using System; using System.Net; using System.Windows; using System.Windows.Controls; using System.Windows.Documents; using System.Windows.Ink; using System.Windows.Input; using System.Windows.Media; using System.Windows.Media.Animation; using System.Windows.Shapes; using Microsoft.Silverlight.Testing; using Microsoft.VisualStudio.TestTools.UnitTesting; namespace Test { [TestClass] public class Test_Svc_Login { [TestMethod] public void Always_True() { Assert.IsTrue(true); } [TestMethod] public void Always_False() { Assert.IsTrue(false); } [TestMethod] public void Even_MoreAlways_False() { Assert.IsTrue(false); } } } </code></pre> 6. Hit F6, try to compile. Everything should be ok at this point. 7. Find the file "App.xaml.cs" in your project. Inside this file you will find the following statement. Of course "new Gui.MainPage();" will be different in your project. Just search for RootVisual. <pre><code> this.RootVisual = new Gui.MainPage(); </code></pre> You replace this statement with the following code block. <pre><code>#if DEBUG if (System.Diagnostics.Debugger.IsAttached) { //You hit F5 ONLY this.RootVisual = new Gui.MainPage(); } else { //You hit CTRL + F5 RunUnitTests(); } #else //You are in Release Mode. You hit whatever you want. this.RootVisual = new Gui.MainPage(); #endif </code></pre> Now you add the following routine to your App.xaml.cs class: <pre><code> private void RunUnitTests() { #if DEBUG //You hit CTRL + F5 var settings = new UnitTestSettings(); settings.TestHarness = new UnitTestHarness(); settings.StartRunImmediately = true; settings.TestAssemblies.Add(Assembly.GetExecutingAssembly()); this.RootVisual = UnitTestSystem.CreateTestPage(settings); #endif } </code></pre> 8. Hit F6 to check if everything is ok. 9. Hit F5 to see, if you can still debug normally. Hit Ctrl+F5 to start the Unit Test. 10. You are done! Now you can unit test in Silverlight 5. Please keep in mind, that the two DLLs from the toolkit are still in "experimental" mode. There is no official support. Also keep in mind, that is approch is about running the tests inside your project. Now you could even run these test at a clients machine in release mode. If want to do that, you have to change #if DEBUG statements, but I think you see what it's all about. Of course you can change this approach to unit test in an extra project. Happy Coding. HINT: If you have problems with System.Core.dll after registering the two DLLs, just use gacutil to register the System.Core.dll again. Like this: gacutil /i "C:\Program Files\Reference Assemblies\Microsoft\Framework\Silverlight\v5.0\System.Core.dll"
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSilverlight Unit Testing
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USMichael
UserOwnerUserId
1. USMichael
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThank you veeeery much!! This is exactly what I was looking for and worked great. I had the System.Core problem you mentioned, but re-registering that also worked.
 singulars
 PostPostId
 PO
 UserUserId
 USMartin Lottering

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.