[SERVER-58386] assign unique collection names to test cases in null_query_semantics.js Created: 09/Jul/21  Updated: 29/Oct/23  Resolved: 16/Jul/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.4, 5.1.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
related to SERVER-58722 assign unique collection names to tes... Closed
related to SERVER-58768 assign unique collection names to tes... Closed
is related to SERVER-58385 recovery oplog application updates mu... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.0
Sprint: Execution Team 2021-07-26
Participants:
Linked BF Score: 33

 Description   

This test repeatedly drops and recreates the same collection for every test case. This can get confusing when diagnosing test failures especially in passthrough suites.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 20/Sep/21 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-58386 clean up null_query_semantics.js to use different collection name for each test case

(cherry picked from commit eb698c09c83f54ed1793de7c9dd7e1aa542f2373)
Branch: v5.0
https://github.com/mongodb/mongo/commit/dad4cfdc548fb32cf44fbad92487388b0705d1d3

Comment by Githook User [ 16/Jul/21 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-58386 clean up null_query_semantics.js to use different collection name for each test case
Branch: master
https://github.com/mongodb/mongo/commit/eb698c09c83f54ed1793de7c9dd7e1aa542f2373

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