WinUI Unit testing with UIFact doesn't appear to work. about xunit.stafact HOT 18 OPEN

Thanks for the write-up. [UIFact] is a framework-agnostic attribute that just emulates common things like a generic SyncContext to keep test execution on a single thread.
It sounds like WinUI has its own specialized SyncContext, which is similar to WinForms and WPF and why they eachhave their own attributes. Cocoa has its own fact too. If you can help us understand the specific requirements for emulating a WinUI main thread, adding support for that sounds good.

As for the issues you ran into, that sounds like it might have just been an issue with how you patched and used the modified DLL.

I'm happy to take a look as well. Where did you get the DispatcherQueueSynchronizationContext type? I don't see it available.

from xunit.stafact.

from xunit.stafact.

The Microsoft.WindowAppSDK package doesn't appear on nuget.org. I can't help make this work without the sync context type that you're talking about.

from xunit.stafact.

from xunit.stafact.

No. I don't know how ***@***.*** would help.

from xunit.stafact.

from xunit.stafact.

from xunit.stafact.

Thanks. Ya your image attachments are not coming from your email to the github issue comment. But your link worked. Apparently the nuget package ID is slightly different than you originally quoted (a typo, no doubt). I should be able to look into this now. Probably sometime next week.

from xunit.stafact.

So I gave this a shot. You can review it here.

This isn't as simple as it sounded. To create a DispatcherQueueSynchronizationContext, I need a DispatcherQueue as well, but these things aren't directly creatable it seems. How does one get one of these?

It sounds like you actually had a compilable thing that you expected to work, though it didn't. I'm finding it quite difficult to get something remotely close to working. So anything you can share from your original prototype would help expedite this.

from xunit.stafact.

from xunit.stafact.

from xunit.stafact.

from xunit.stafact.

Thanks for the blog link. I guess I have to create a Window object to get its DispatcherQueue property from it. I'm trying with that now.

the exception text in WaitForOperationCompletionAsync says WPF not WinUI.

Thanks. Fixed.

The exception itself is concerning. I will need to test async methods that must be run on the UI thread. The message says no “async void”. Does that mean “async Task” are ok? You have such tests in WpfFactTests.cs, so I’m guessing they are, but staring at the code in the diff tells me nothing.

Yes, async Task test methods are fine. It's the async void tests that don't work.

from xunit.stafact.

I've made a lot of progress. But the blog post is 2+ years old, and I had to make some changes to get WinUI tests building the way it proposed. But they don't run even with UITestMethod attributes. And the blog outlines some tight-knit interactions between the test runner and test framework, and assume that the test runner will execute the .exe instead of loading the test assembly as a library into another process. I don't know if xunit can do this. This could require xunit changes as well.

Latest changes

from xunit.stafact.

from xunit.stafact.

Yes, I understand the concession may include running an .exe. But unless you know of a way to get xunit tests to execute within an .exe test project that launches itself instead of by way of the xunit or dotnet test test runners, I don't see how we can make this work with xunit.

from xunit.stafact.

from xunit.stafact.

I don't know how you would make this work at this point. And xunit.stafact as an xunit library that your test project loads isn't properly positioned to spin up xunit.

from xunit.stafact.