Skip to content

Add autouse fixtures to restore server state in setFeatureCompatibilityVersion tests#668

Open
alinaliBQ wants to merge 1 commit into
documentdb:mainfrom
alinaliBQ:fix-setFeatureCompatibilityVersion
Open

Add autouse fixtures to restore server state in setFeatureCompatibilityVersion tests#668
alinaliBQ wants to merge 1 commit into
documentdb:mainfrom
alinaliBQ:fix-setFeatureCompatibilityVersion

Conversation

@alinaliBQ

Copy link
Copy Markdown
Contributor

Tests that mutate global server FCV (setFeatureCompatibilityVersion) previously relied on inline restore calls
after assertions. If an assertion failed, the restore was skipped, leaking mutated state into every subsequent test.

Signed-off-by: Alina (Xi) Li <Alina.Li@improving.com>
@alinaliBQ alinaliBQ marked this pull request as ready for review July 7, 2026 19:09
@alinaliBQ alinaliBQ requested a review from a team as a code owner July 7, 2026 19:09
@documentdb-triage-tool documentdb-triage-tool Bot added compatibility test Compatibility test related enhancement New feature or request labels Jul 7, 2026
@documentdb-triage-tool

Copy link
Copy Markdown

🤖 Auto-triaged by documentdb-triage-tool.

Applied: compatibility test, enhancement
Project fields suggested: Component test-coverage · Priority P2 · Effort M · Status Needs Review
Confidence: 0.75 (mixed)

Reasoning

component from path globs (test-coverage); effort from diff stats (33+4 LOC, 4 files); LLM: Fixes a test-isolation bug where failed FCV assertions leak mutated global state into subsequent tests, causing unreliable test results.

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.

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

Labels

compatibility test Compatibility test related enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant