DevForce Community Forum : Unit Testing GetEntitiesAsync http://www.ideablade.com/forum/ This is an XML content feed of; DevForce Community Forum : DevForce Classic : Unit Testing GetEntitiesAsync Wed, 10 Jun 2026 20:54:46 -700 Wed, 07 Jan 2009 11:51:43 -700 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 9.69 360 www.ideablade.com/forum/RSS_post_feed.asp?TID=1040 DevForce Community Forum http://www.ideablade.com/forum/forum_images/IdeaBlade_logo_tm.png http://www.ideablade.com/forum/ Unit Testing GetEntitiesAsync : Thanks Kim. I'll give that... http://www.ideablade.com/forum/forum_posts.asp?TID=1040&PID=3785#3785 Author: kid_kaneda
Subject: 1040
Posted: 07-Jan-2009 at 11:51am

Thanks Kim. I'll give that a try]]> Wed, 07 Jan 2009 11:51:43 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=1040&PID=3785#3785 Unit Testing GetEntitiesAsync : You can unit test async calls... http://www.ideablade.com/forum/forum_posts.asp?TID=1040&PID=3762#3762 Author: kimj
Subject: 1040
Posted: 31-Dec-2008 at 6:28pm

You can unit test async calls in MSTest or NUnit, etc, it just takes a little extra effort.  The error you see is the PersistenceManager complaining about a thread synchronization problem which you can work around.
 
The easiest, although possibly not the most robust, way to solve the problem is to set the appropriate SynchronizationContext at the beginning of your test (or in a test or class initializer), like so:
 
   SynchronizationContext sc = new System.Windows.Forms.WindowsFormsSynchronizationContext();
   System.Windows.Forms.WindowsFormsSynchronizationContext.SetSynchronizationContext(sc);
 
Once set, you can then issue async calls from your test method without the PM throwing an exception.
 
Our own unit test suite for the framework actually uses a more complex (and possibly convoluted) approach to async unit testing which involves creating a form for each test.
 
 
]]> Wed, 31 Dec 2008 18:28:57 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=1040&PID=3762#3762 Unit Testing GetEntitiesAsync : GetEntitiesAsynch expects to be... http://www.ideablade.com/forum/forum_posts.asp?TID=1040&PID=3758#3758 Author: davidklitzke
Subject: 1040
Posted: 31-Dec-2008 at 9:11am

GetEntitiesAsynch expects to be run in an Environment where there is a main UI thread and the GetEntitiesAsynch thread is spawned by the main UI thread.  Normally, this is done by running your application as a Windows Forms Application, but the error message indicates that if you are using a Console or WindowsService application, you must use BeginInvoke and EndInvoke mechanisms instead.  Alternatively, you might might be able to write your unit test application as a Windows Forms Application.

Edited by davidklitzke - 31-Dec-2008 at 9:15am]]> Wed, 31 Dec 2008 09:11:22 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=1040&PID=3758#3758 Unit Testing GetEntitiesAsync : Hi I'm trying to write... http://www.ideablade.com/forum/forum_posts.asp?TID=1040&PID=3756#3756 Author: kid_kaneda
Subject: 1040
Posted: 31-Dec-2008 at 3:21am

Hi
 
I'm trying to write a unit test which gets data asynchronously using GetEntitiesAsync().  When I run this under MSTest I get the following exception (including the xxx at the beginning):
 
"xxxAsync methods can only be called from applications running in a SynchronizationContext that supports thread synchronization. This means, in general, applications running in a WinForms or ASP.NET environment.  Console or WindowsService applications must use BeginInvoke and EndInvoke mechanisms instead"
 
Does this mean the async calls to the PersistenceManager cannot be tested?
 
Thanks
 
Kaneda
]]> Wed, 31 Dec 2008 03:21:04 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=1040&PID=3756#3756