[SERVER-82508] Print out command response in assertions on response in bulkWrite js tests Created: 27/Oct/23 Updated: 02/Nov/23 Resolved: 02/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kaitlin Mahar | Assignee: | Kaitlin Mahar |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 151 | ||||||||
| Description |
|
In the bulkWrite jstests we assert extensively on values from responses to the bulkWrite command. However, when these assertions fail they can be very difficult to debug because we don't print out the full command response. E.g. in BF-30586 we can't say definitively which error we expected to see in the response but didn't see. We should augment the assert.eq calls with a message to print out the response in the case that they fail. |
| Comments |
| Comment by Githook User [ 02/Nov/23 ] |
|
Author: {'name': 'Kaitlin Mahar', 'email': 'kaitlin.mahar@mongodb.com', 'username': 'kmahar'}Message: |