[SERVER-22422] Test that write commands support writeConcern Created: 01/Feb/16 Updated: 20/Nov/16 Resolved: 12/Apr/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Write Ops |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.8, 3.3.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Judah Schvimer |
| Resolution: | Done | Votes: | 0 |
| Labels: | test-only | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Backport Completed: | |
| Sprint: | Sharding 10 (02/19/16), Sharding 11 (03/11/16), Sharding 12 (04/01/16), Sharding 13 (04/22/16) |
| Participants: |
| Description |
|
write commands need to be tested that they support write concern. Since the writeConcern logic is centralized not every command must be tested. Rather commands of different types, especially those that already handled write concern on their own, or User Management Commands that have special response formats, should be tested. |
| Comments |
| Comment by Githook User [ 17/Jun/16 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: |
| Comment by Eric Milkie [ 16/Jun/16 ] |
|
Backport of only the change to shardingtest.js requested by gabriel.russell |
| Comment by Githook User [ 12/Apr/16 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: |