[SERVER-44423] Audit use of assert.writeError in sharding tests Created: 05/Nov/19 Updated: 12/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | sharding-nyc-test-improvements | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Cluster Scalability
|
| Participants: |
| Description |
|
A few tests in jstests/sharding use assert.writeError() to verify a command will fail, but this assertion passes with any error code, so it's possible for behavior to change without these tests catching it. We should look through the tests that use this assertion and change them to use assert.commandFailedWithCode() so we can be more confident in our regression testing. |