This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Support custom output formatters #9
Labels
Comments
Merged
|
Parameters passed to formatters should include the number of pending examples, as described in #38. At that point pending examples should stop printing directly via |
modocache
changed the title
modocache
changed the title
modocache
added a commit
that referenced
this issue
Jun 28, 2014
Prior to this commit, Nimble would report failures via XCTFail. While this allows for a complete separation of Quick and Nimble, it is inflexible--if expectations are placed within a shared example group, for example, Quick has no way of reporting the failures accurately. Quick now reports failures via exceptions. Nimble raises exceptions to indicate failures, with details on the file and line number of the failed expectation embedded within the raised exception's user info. This paves the way for shared examples #44 and custom output formatters #9. Other changes of note: - Remove API to override failure reporting in QuickSpec. Since QuickSpec uses SenTestingKit file and line number keys anyway, the issue raised in #41 can still be considered resolved - Rename Callsite_ to Callsite--I don't know how I missed this in the pull request review
modocache
changed the title
Closed
|
What's the status on this? |
|
This is a sort of "wishlist" feature, I'm not working on it at the moment. :) |
ikesyo
pushed a commit
that referenced
this issue
Sep 3, 2016
[NSBundle+CurrentTestBundle] Use `first(where:)`
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Luckily, some nerd wrote down how RSpec implements custom output formatters.
An example in Objective-C can be found here: kiwi-bdd/Kiwi#449
I wonder if it'd be possible to implement an output formatter that aggregates results and displays an OS X notification with a breakdown of passed, pending, failed, and errored?
The text was updated successfully, but these errors were encountered: