Xcode-beta (7A152u): Special Handling of Code Paths with Fatal Errors in Test Coverage
| Originator: | john | ||
| Number: | rdar://21786174 | Date Originated: | 12-Jul-2015 02:50 PM |
| Status: | Open | Resolved: | |
| Product: | Developer Tools | Product Version: | Xcode-beta (7A152u) |
| Classification: | Feature (New) | Reproducible: | Always |
Summary: When writing unit tests, there is no way to test fatal errors. They immediately cause the entire test suite to stop. This makes a certain amount of sense, because fatal errors are best reserved for things that are either impossible or invalid. However, this causes noise in the code coverage. This code can’t be invoked by the test suite, and is thus showing up as untested. This can cause visual noise and make it harder to quickly scan through files for legitimately untested code. I think it might make sense to highlight these cases in some other way. Steps to Reproduce: Expected Results: Actual Results: Regression: Notes:
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!