Open KentLottis-jwn opened 1 year ago
Note: one might think that this is actually an issue with Quick, since it concerns test-case enumeration (a Quick behavior) as opposed to assertion handling (the core Nimble behavior). However, if I replace the expect()
clause with an equivalent XCTAssertEqual("b", "a")
, then the test case is enumerated as desired.
Note: one might think that this is actually an issue with Quick, since it concerns test-case enumeration (a Quick behavior) as opposed to assertion handling (the core Nimble behavior). However, if I replace the expect() clause with an equivalent XCTAssertEqual("b", "a"), then the test case is enumerated as desired.
Fascinating. That doesn't seem like that should be the case.
What did you do?
We found a malformed spec that had gone undiscovered under older versions of Quick/Nimble. Specifically, the spec author had failed to nest an
expect()
clause inside anit()
block. Previously, this was silently ignored. Now it results in no tests being executed.What did you expect to happen?
Ideally, we would get some sort of run-time diagnostic pointing to the coding error. At the very least, the other well-formed test cases in the spec should execute normally.
What actually happened instead?
The spec fails to run any tests.
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
Easier to just paste in the repro case
I would expect this spec to result in one test failure. Instead, not tests are executed.