You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For Nimble version 9.2.1 on Xcode 14/15 while using toEventually on expect that is returning results from UI for example a view getting hidden/displayed, count on UITableView's rows etc, is it advisable to use toEventually for such validations as mentioned above ? Will it lead to any main runloop getting stopped or unresponsive kind of issues ? What is the best practice to use Nimble while writing unit tests that also includes UI for example UIViewController/UIView etc?
The text was updated successfully, but these errors were encountered:
For Nimble version
9.2.1
on Xcode 14/15 while usingtoEventually
onexpect
that is returning results from UI for example a view getting hidden/displayed, count on UITableView's rows etc, is it advisable to usetoEventually
for such validations as mentioned above ? Will it lead to any main runloop getting stopped or unresponsive kind of issues ? What is the best practice to use Nimble while writing unit tests that also includes UI for example UIViewController/UIView etc?The text was updated successfully, but these errors were encountered: