Investigate changes in PM-1804: API version testing

    • Type: Epic
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • Needed
    • None
    • None
    • None
    • None
    • None
    • None

      Downstream Change Summary

      Specific changes will be noted in SERVER tickets and downstream attention emails

      Description of Linked Ticket

      Epic Summary

      Summary

      Versioned MongoDB API (PM-1792) will have its own targeted testing of the APi functionality. This epic will cover work to create a comprehensive API version testing framework to ensure we do not introduce unintended API-breaking changes without bumping the API version. (e.g. "make sure we don't break $ positional projection between releases")

      Motivation

      PM-1792 introduces API versioning to the server. Its scope defines the commands included in API Version 1 and the definition of a breaking change that requires introducing a new API version. This project is to create automated testing that ensures Server engineers cannot introduce a breaking change without introducing a new API version.

      Cast of Characters

      • Product Owner:
      • Project Lead:
      • Program Manager:
      • Drivers Contact:

      Documentation

      Scope Document
      Technical Design Document

            Assignee:
            Unassigned
            Reporter:
            Backlog - Core Eng Program Management Team
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None
              None
              None
              None
              None