[MCP] Investigate E2E test flakyness with Service accounts

XMLWordPrintableJSON

    • Type: Investigation
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • APIx DevTools

      Goal

      Timebox investiagation to figure out the flakyness with service accounts. 

      • If needed, fix the test to remove the length check to check only the expected organization.

       

      Context

      bianca.vianadeaguiar@mongodb.com, filipe.menezes@mongodb.com, the integration tests for Atlas are failing in main because there seems to have been some configuration changes in the atlas organisation it's using:

       ❯  unit-and-integration  tests/integration/tools/atlas/orgs.test.ts (2 tests | 1 failed) 366ms
         ✓ atlas > orgs > atlas-list-orgs > should have correct metadata 8ms
         × atlas > orgs > atlas-list-orgs > returns org names 314ms
           → expected [ { …(1) }, { …(1) } ] to have a length of 1 but got 2

      are you aware of this? how should we fix this?

      edit: the run is https://github.com/mongodb-js/mongodb-mcp-server/actions/runs/16626573533/job/47044547828
      Created with Jira Integration+ for bianca.vianadeaguiar (bianca.vianadeaguiar@mongodb.com)

              Assignee:
              Unassigned
              Reporter:
              Bianca Lisle
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: