Add setParameter tests

[alinaliBQ]

Add command operator tests for setParameter. Tests database setParameter behavior, output collection, syntax, and errors. Worked with @vic-tsang to get initial set of tests to work with.

• Add compatibility test for setParameter #432

[documentdb-triage-tool]

🤖 Auto-triaged by documentdb-triage-tool.

Applied: compatibility test, enhancement
Project fields suggested: Component test-coverage · Priority P2 · Effort L · Status Needs Review
Confidence: 0.30 (deterministic)

Reasoning

component from path globs (test-coverage); effort from diff stats (757+0 LOC, 6 files); LLM failed: Invalid response body while trying to fetch https://api.anthropic.com/v1/messages: Premature close

If a label is wrong, remove it manually and ping @patty-chow so the rules can be tuned. The bot will not re-label items that already have component labels.

[manojnks]

https://www.mongodb.com/docs/manual/reference/parameters/
only partial of thing available here are tested.
should this feature test all the parameters?

[manojnks]

AdministrationTestCase this has been introduced for getClusterParameter should use that here?

[alinaliBQ]

should this feature test all the parameters?

I believe testing all the parameters is not required for this feature. Since different BSON types are accepted by setParameter, the test suite verifies that the operator works as expected. Also the TEST_COVERAGE.md guide has a "No engine-specific implementation details" rule which excludes the internal parameters such as internalSessionsReapThreshold.

AdministrationTestCase this has been introduced for getClusterParameter should use that here?

I think it is optional since CommandTestCase structure works with setParameter. In general we try to use existing command test cases if possible to avoid conflicts.

[alinaliBQ]

@manojnks Please let me know if you have any other comments, thanks

[manojnks]

sounds good

[eerxuan]

tests nothing and duplicates no_param_pair.

[eerxuan]

1. All 5 files — state restoration is failure-unsafe; a failed assertion leaks mutated global parameters into every later test. Fix structurally with an autouse snapshot/restore
   fixture rather than ~20 copies of inline restore-after-assert.
2. Several tests restore to a hardcoded default instead of the captured original — corrupting state even on success.