[SERVER-23547] Multiversion test framework should allow running minor versions that share a major version with latest Created: 05/Apr/16  Updated: 25/Jan/17  Resolved: 07/Apr/16

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: 3.2.4, 3.3.4
Fix Version/s: 3.2.5, 3.3.5

Type: Improvement Priority: Major - P3
Reporter: Andy Schwerin Assignee: Andy Schwerin
Resolution: Done Votes: 0
Labels: test-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Backport Completed:
Sprint: Sharding 13 (04/22/16)
Participants:

 Description   

Instead of corresponding to any MongoDB version on the latest branch or its development version, "latest" should correspond only to the same MongoDB version as the running shell. This way, it will be possible to write multiversion tests that compare the behavior of different minor versions in the same release, i.e. 3.2.1 vs 3.2.5.



 Comments   
Comment by Githook User [ 07/Apr/16 ]

Author:

{u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}

Message: SERVER-23547 Make the multiversion concept of "latest" more precise.

This supports multiversion tests involving subversions, like 3.2.1 compared to 3.2 latest.
Branch: v3.2
https://github.com/mongodb/mongo/commit/0953a237e58d2af33a55c420d8aefbbb3d4ff88b

Comment by Githook User [ 07/Apr/16 ]

Author:

{u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}

Message: SERVER-23547 Make the multiversion concept of "latest" more precise.

This supports multiversion tests involving subversions, like 3.2.1 compared to 3.2 latest.
Branch: master
https://github.com/mongodb/mongo/commit/07c2cd5b87e44e5f95fe4f6bdfef5fb6dd012bce

Generated at Thu Feb 08 04:03:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.