[SERVER-74536] Consolidate move_range_basic.js and move_range_max_bound.js after 7.0 branches out Created: 02/Mar/23 Updated: 29/Oct/23 Resolved: 04/Jul/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Allison Easton |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | 7.0UpDown | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2023-07-10 |
| Participants: |
| Description |
|
The test added in move_range_max_bound.js has the same setup as move_range_basic.js and was only added as a separate file to allow move_range_basic.js to continue being run in multiversion scenarios. Once 7.0 branches out, we can remove move_range_max_bound.js and add the test cases into move_range_basic.js. |
| Comments |
| Comment by Githook User [ 04/Jul/23 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |