[SERVER-25458] unit tests for ShardingState::initializeShardingAwarenessIfNeeded Created: 05/Aug/16 Updated: 19/Nov/16 Resolved: 15/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.14 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 2016-08-29, Sharding 2016-09-19, Sharding 2016-10-10 | ||||||||
| Participants: | |||||||||
| Description |
|
The unit test infrastructure should be reorganized slightly to prevent duplicate code in multiple fixtures. Currently, this method is part of the ShardingState class, whose methods are either tested on the ShardingStateTest fixture or not unit tested. This is largely because the ShardingStateTest fixture has neither:
Rather than making ShardingStateTest yet another test fixture that implements functionality needed to use the NetworkInterfaceMock or ServiceContextMongoDTest (in its setUp() method), the sharding test fixtures should be reorganized for better inheritance and modularity. See |
| Comments |
| Comment by Githook User [ 15/Sep/16 ] |
|
Author: {u'name': u'Esha Maharishi', u'email': u'esha.maharishi@mongodb.com'}Message: |