[SERVER-66055] Document how multiversion testing works Created: 28/Apr/22  Updated: 29/Oct/23  Resolved: 07/Sep/22

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 6.2.0-rc0

Type: Improvement Priority: Major - P3
Reporter: David Bradford (Inactive) Assignee: Mikhail Shchatko
Resolution: Fixed Votes: 0
Labels: dp-qol
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: DAG 2022-05-16, DAG 2022-09-05, DAG 2022-09-19
Participants:
Story Points: 3

 Description   

Our multiversion testing support is very complicated. We have lots of concepts like last_lts vs last_continuous, old vs new, multiversion tags, version_combinations, etc. It can be difficult to know what all this means as how to understand what is going on with multiversion tests. We should document how multiversion testing works, what the multiverison terminology means, and how engineers are expected to interact with multiversion testing.


As a database contributor,
I want to documentation for multiversion testing,
So that I can understand how it works.


AC:

  • A page exists here describing multiversion testing.
  • The documentation should include:
    • Definitions of multiversion terminology.
    • An overview of how multiversion testing works.
    • Anything engineers should know when working with multiversion tests.


 Comments   
Comment by Githook User [ 07/Sep/22 ]

Author:

{'name': 'Mikhail Shchatko', 'email': 'mikhail.shchatko@mongodb.com', 'username': 'MikhailShchatko'}

Message: SERVER-66055 Document how multiversion testing works
Branch: master
https://github.com/mongodb/mongo/commit/86f3153cecf9e2e6de994d852c2317a37abac2c5

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