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
I have read CONTRIBUTING and have done my best to follow them.
What did you do?
When running tests, the developer has the option to click on the red diamond on Xcode's gutter to re-run tests. When the top most diamond is actioned, the tests correctly failed, but when the failing test's local diamond is actioned, Xcode reports the test as a success despite the code not being changed. See the sample project and the video demoing the problem.
QuickNimbleFailureSuccess.mov
What did you expect to happen?
I expected the test to correctly fail or succeed.
What actually happened instead?
The test succeeded even though it should have failed.
Environment
List the software versions you're using:
Quick: 4.0.0
Nimble: 9.2.1
Xcode Version: Version 13.2.1 (13C100)
Swift Version: Xcode Default
Please also mention which package manager you used and its version. Delete the
other package managers in this list:
Related note: I was hoping that I could use the control + option + command + U shortcut to re-run the selected current test case, but that seems to only work for XCTest methods, not for Quick/Nimble. See how that menu item is disabled. Any known workaround for that?
Seems to be a regression introduced by #1143 which reverted 90ec83d .
I'm using Xcode 13.4.1 and when running a focused test testSuiteForTestCaseWithName: is not called so it seems necessary to swizzle testClassSuitesForTestIdentifiers:skippingTestIdentifiers:randomNumberGenerator: .
However @younata tested it as part of #1143 and it worked, perhaps a different Xcode version?
What did you do?
When running tests, the developer has the option to click on the red diamond on Xcode's gutter to re-run tests. When the top most diamond is actioned, the tests correctly failed, but when the failing test's local diamond is actioned, Xcode reports the test as a success despite the code not being changed. See the sample project and the video demoing the problem.
QuickNimbleFailureSuccess.mov
What did you expect to happen?
I expected the test to correctly fail or succeed.
What actually happened instead?
The test succeeded even though it should have failed.
Environment
List the software versions you're using:
Please also mention which package manager you used and its version. Delete the
other package managers in this list:
Project that demonstrates the issue
QN.zip
The text was updated successfully, but these errors were encountered: