StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19015963
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-09-25T22:05:32.550
FavoriteCount
0
LastActivityDate
2018-07-25T08:23:47.953
LastEditDate
2018-07-25T08:23:47.953
LastEditorUserId
2830676
OwnerUserId
393615
ParentId
18914544
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
I would suggest that you provide you own <code>IScheduler</code> implementation to <code>ObserveOn(IScheduler)</code> instead of using the <code>ObserveOnDispatcher()</code> operator. I have used techniques for loading a <code>DispatcherFrame</code> or a <code>Dispatcher</code> but the problem is that you are still using a Dispatcher. Eventually I found that you just "fall off the cliff" especially once you have long running background threads involved. Following the guidelines of "No threading in Unit tests" just dont let the dispatcher get near your ViewModels! Your Unit tests will run much, much faster. A far superior way to deal with this is to inject an interface that gives access to your Dispatcher Scheduler (via the <code>IScheduler</code> interface). This allows you to substitute in an implementation that exposes the <code>TestScheduler</code>. You now can control time in your unit test. You can control and validate which actions are marshalled to each scheduler. This is a really old (pre-Rx) post on 'Unit' testing WPF with Dispatcher calls from early 2009. It seemed like a good idea at the time. <a href="https://leecampbell.com/2009/02/17/responsive-wpf-user-interfaces-part-5/" rel="nofollow noreferrer">https://leecampbell.com/2009/02/17/responsive-wpf-user-interfaces-part-5/</a> More information on Testing with Rx and the <code>TestScheduler</code> is found in my other site on Rx <a href="http://introtorx.com/Content/v1.0.10621.0/16_TestingRx.html" rel="nofollow noreferrer">http://introtorx.com/Content/v1.0.10621.0/16_TestingRx.html</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORx reactive extensions Observeondispatcher unit test error: The current thread has no Dispatcher associated with it
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USYitzchak
UserOwnerUserId
1. USLee Campbell
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PORx reactive extensions Observeondispatcher unit test error: The current thread has no Dispatcher associated with it
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

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.