[SERVER-53740] Implicitly setup the database in ConfigServerTestFixture::setupCollection Created: 13/Jan/21  Updated: 22/Jan/21  Resolved: 22/Jan/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
Resolution: Done Votes: 0
Labels: Sharding-EMEA, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

Some tests using the ConfigServerTestFixture are currently relying on inconsistent metadata not emulating a real context:
ConfigServerTestFixture::setupCollection is populating config.collections with a collection document. However,
it must also check whether a database entry already exists in config.databases and - if not - implicitly initialize it by calling ConfigServerTestFixture::setupDatabase.



 Comments   
Comment by Githook User [ 22/Jan/21 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-53740 Implicitly setup the database in ConfigServerTestFixture::setupCollection
Branch: master
https://github.com/mongodb/mongo/commit/f2edde9de318c91ad7e711cea6dcc13726fce4b0

Generated at Thu Feb 08 05:31:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.