[MainThreadFact] to execute tests on main thread on macos about xunit.stafact HOT 6 CLOSED

Closed by #68

from xunit.stafact.

Most of the attributes in this library are Windows-specific. But UIFact might work for you. It is OS-agnostic, but really the only thing it does is keep the test running on one particular thread even across async awaits.

I'm a bit surprised to hear of a requirement to only be accessed from the "main thread", since in Windows this is virtually indistinguishable from any other thread. Most thread affinitized libraries I see care about either of two other things:

1. They are not thread-safe, and therefore should only be accessed from one thread, but the particular thread chosen doesn't matter.
2. They access the UI, so they need to only be accessed on the UI thread.

If your native library actually has one of these two common requirements, I think [UIFact] may work for you. But I'm not sure.

If you try it and find that it's insufficient, and are willing to send a PR to this library to add a new attribute to do what macos requires, comment back on this issue with your proposal and I may take a PR.

from xunit.stafact.

i tried
I'll make this issue a feature request then

from xunit.stafact.

I'll need to know what you're requesting then. What is it about UIFact that isn't enough for your native library, for example? I don't have a mac, so this isn't a feature I'm likely to be able to do myself without a precise spec. Can you offer one?

from xunit.stafact.

Unfortunately [UIFact] isn't enough. What di you mean by spec? Main thread is main thread, but i guess it is unavailable to be modified in xunit?

from xunit.stafact.

In Windows, the main thread is the entrypoint thread. No test runner I've seen exposes that for tests. The main thread just sleeps while tests are running (waking up to schedule them, perhaps).
I don't know what it's like on a mac, if macos defines main thread differently. But I suspect the xunit runner on macos is the same, in that it's impossible to get the test to actually run on the entrypoint thread.

So to make progress on this, I think you'll need to research what this native module you're using really means by the main thread. If it means it literally checks to make sure its code is running on the entrypoint thread, there's nothing that can be done there except switch your testing from Xunit to a hand-written exe that runs your own methods as tests. If there are other more flexible requirements about the thread it's on, we may be able to do something here.

from xunit.stafact.