Rachel Brindle
Rachel Brindle
Coming back to this after a few years: I think that Quick should default to executing tests in the order defined in, and for randomization we should rely on the...
This issue appears to have been fixed at some point in the intervening 6 years. My apologies for the frustrations. But in current versions of Quick/Xcode, this is now working.
Bumping this to the next (major?) release in favor of getting async/await support out the door sooner.
Per Matt Gallagher, this is apparently ultimately a bug with lldb on rosetta? His suggestion is to disable "Debug executable" for the test target when you're running under rosetta. https://github.com/mattgallagher/CwlPreconditionTesting/issues/26#issuecomment-1493237957...
At this point, I don't think this is worth doing. It might have been more useful years earlier in the project. Introducing this much of a syntax change to Nimble,...
Hi John! After a bunch of noodling on this, I forked your fork and made a PR that includes these changes + some feedback: https://github.com/Quick/Nimble/pull/1051 This will get merged shortly....
This comment is meant to log when this happens, to help figure out what might be the cause. - [`AsyncTest.testWaitUntilDoesNotCompleteBeforeRunLoopIsWaiting`](https://github.com/Quick/Nimble/actions/runs/3295059969/jobs/5433218101) - [`AsyncTest.testToEventuallyMustBeInMainThread`](https://github.com/Quick/Nimble/actions/runs/3294890538/jobs/5432876695) - [`AsyncTest.testWaitUntilDoesNotCompleteBeforeRunLoopIsWaiting`](https://github.com/Quick/Nimble/actions/runs/3294890538/jobs/5432876476) - [`AsyncTest.testWaitUntilDoesNotCompleteBeforeRunLoopIsWaiting`](https://github.com/Quick/Nimble/actions/runs/3294447558/jobs/5431975948) - A rare non-Async...
> we should just use a different library to test with, and not use Quick? That's not what I'm saying. I'm saying that I'm not interested in bringing in something...
Fascinating. > the move of `spec()` from an instance method to a class method meant that the thread running the test no longer has a run loop? That shouldn't be...
I haven't heard back in over a month on this. I'm going to close this as unable to reproduce.