[SERVER-37365] Relax `.ignore()` requirements for `Status` and `StatusWith< T >` returning functions in `ASSERT_THROWS` type statements. Created: 27/Sep/18 Updated: 29/Oct/23 Resolved: 02/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.4 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | ADAM Martin (Inactive) | Assignee: | ADAM Martin (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Service Arch 2018-10-08 |
| Participants: |
| Description |
|
Although a function which reports its errors by both throwing and bad Status codes is a bad idea, that's no reason to inconvenience those who need to test such functions. We should clean up those functions, but it shouldn't be necessary to explicitly ignore their status returns when testing their throw behavior – the test is sufficient to indicate that `Status` is ignored. |
| Comments |
| Comment by Githook User [ 02/Oct/18 ] |
|
Author: {'name': 'ADAM David Alan Martin', 'email': 'adam.martin@10gen.com', 'username': 'adamlsd'}Message: It shouldn't be necessary to explicitly ignore status returns in |