set_param1.js should only compare what it sets

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2026-01-19
    • 200
    • 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None

      The test

      • sets a logLevel parameter 
      • runs getParameter and compares the result 
        The comparison is misleading, because it compares the entire result of getParameter instead of checking just the logLevel param.
        Previous tests can modify different parameters, and some tests might modify only a parameter on a specific mongos. If getParameter is executed randomly, it might return false negatives

            Assignee:
            Enrico Golfieri
            Reporter:
            Enrico Golfieri
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: