Skip to content

test(NODE-7426): Add appName to OIDC test failpoints#4869

Open
PavelSafronov wants to merge 2 commits intomongodb:mainfrom
PavelSafronov:NODE-7426
Open

test(NODE-7426): Add appName to OIDC test failpoints#4869
PavelSafronov wants to merge 2 commits intomongodb:mainfrom
PavelSafronov:NODE-7426

Conversation

@PavelSafronov
Copy link
Contributor

@PavelSafronov PavelSafronov commented Feb 9, 2026

Description

Summary of Changes

Updated OIDC test specs.
Double-checked that failpoints are being removed
Updated UnifiedMongoClient to always configure an appName, as either a passed-in value or a unique identifier, as called out for OIDC tests in mongodb/specifications@4d11668

Double check the following

  • Lint is passing (npm run check:lint)
  • Self-review completed using the steps outlined here
  • PR title follows the correct format: type(NODE-xxxx)[!]: description
    • Example: feat(NODE-1234)!: rewriting everything in coffeescript
  • Changes are covered by tests
  • New TODOs have a related JIRA ticket

@PavelSafronov PavelSafronov marked this pull request as ready for review February 10, 2026 20:07
@PavelSafronov PavelSafronov requested a review from a team as a code owner February 10, 2026 20:07
@dariakp dariakp self-assigned this Feb 18, 2026
@dariakp dariakp added the Primary Review In Review with primary reviewer, not yet ready for team's eyes label Feb 18, 2026
}

// Test descriptions use `appName` and `appname` interchangeably
if (
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should not need to modify the unified test runner, since there was no change to the unified test runner specification. The appName for unified tests is already passed in directly via the spec files themselves.

You may find it helpful to look at the reference implementations linked in the spec PR (mongodb/specifications#1891), for example the python one here.

});

afterEach(async function () {
// explicitly remove the fail point to prevent interaction betweet test runs
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The annotations are helpful, however, the new requirement in the spec is to ensure that we not only remove the failpoint but also always set the appName for any failpoint created. In this file, there are two types of clients - the regular one and the util client (with the util clients being used to set fail points), with some clients instantiated via new MongoClient and others via the getClient method, so we want to make sure that we always configure the clients being tested and the failpoints set in the test with an appName.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Primary Review In Review with primary reviewer, not yet ready for team's eyes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments