Skip to content

Improve project extension test diagnostics - #14737

Draft
rainersigwald wants to merge 1 commit into
mainfrom
raines-improve-projectextensions-test-diagnosti
Draft

Improve project extension test diagnostics#14737
rainersigwald wants to merge 1 commit into
mainfrom
raines-improve-projectextensions-test-diagnosti

Conversation

@rainersigwald

@rainersigwald rainersigwald commented Aug 18, 2026

Copy link
Copy Markdown
Member

Project-extension import tests were relying on a shared temp directory and weak assertions, so failures could be opaque and environment-sensitive. This change isolates each test case and adds explicit diagnostics so the DoesNotImportProjectIfNotExist path is easier to reason about and reproduce.

Changes Made

  • moved the shared import fixture to isolated TestEnvironment/TransientTestFolder state per test
  • added ITestOutputHelper logging for the evaluated MSBuildProjectExtensionsPath
  • tightened assertions with explicit Shouldly checks and ShouldHaveSingleItem() expectations
  • aligned the props/targets subclasses with the new fixture pattern

This should improve a flaky failure that hit #14280.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 1e6c3658-5713-4ecf-a884-15be42c4305f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant