Conversation
Agent-Logs-Url: https://github.com/microsoft/testfx/sessions/b1573313-b7dd-4dca-a827-51d1ada1e918 Co-authored-by: Evangelink <11340282+Evangelink@users.noreply.github.com>
Agent-Logs-Url: https://github.com/microsoft/testfx/sessions/b1573313-b7dd-4dca-a827-51d1ada1e918 Co-authored-by: Evangelink <11340282+Evangelink@users.noreply.github.com>
AppVersion and remove CrashDump IVT dependency
|
@copilot pipeline is red, please fix issues |
Agent-Logs-Url: https://github.com/microsoft/testfx/sessions/073d3d20-d294-468e-82ba-4e708f8126f1 Co-authored-by: Evangelink <11340282+Evangelink@users.noreply.github.com>
Pushed a fix in Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
|
@copilot there is a test failure: Check failure on line 665 in src/TestFramework/TestFramework/Assertions/Assert.AreEqual.cs @azure-pipelines src/TestFramework/TestFramework/Assertions/Assert.AreEqual.cs(665,1): error : [NewerPlatform_WithPreviousExtensions_ShouldExecuteTests] [net11.0] Assert.AreEqual failed. Expected:<0>. Actual:<1>. 'expected' expression: 'exitCode', 'actual' expression: 'testHostResult.ExitCode'. Expression 'AssertExitCodeIs' failed for member 'NewerPlatform_WithPreviousExtensions_ShouldExecuteTests' at line 17 of file '/_/test/IntegrationTests/Microsoft.Testing.Platform.Acceptance.IntegrationTests/ForwardCompatibilityTests.cs'. Output of the test host is:
|
Agent-Logs-Url: https://github.com/microsoft/testfx/sessions/ceb77044-bf71-4acf-8113-6c0af8aee63c Co-authored-by: Evangelink <11340282+Evangelink@users.noreply.github.com>
Fixed in Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
AppVersion and remove CrashDump IVT dependencyAppVersion while preserving CrashDump forward compatibility
|
@copilot let's avoid reflection and instead ujse the same technic as the core platform (with the msbuild template) |
Agent-Logs-Url: https://github.com/microsoft/testfx/sessions/ec83e2ad-9aa5-43e1-8ea7-e05680c869f2 Co-authored-by: Evangelink <11340282+Evangelink@users.noreply.github.com>
Done in |
AppVersion while preserving CrashDump forward compatibilityAppVersion using MSBuild-generated build info while preserving CrashDump forward compatibility
…rsion wrapper - Move BuildInfo.cs.template to SharedExtensionHelpers/ as a single shared copy - Add BuildInfoTemplateFile property in Directory.Build.targets to allow overriding the template path (defaults to MSBuildProjectDirectory) - Extension csproj files now set BuildInfoTemplateFile to the shared template - Template now generates ExtensionVersion.DefaultSemVer directly, eliminating the unnecessary ExtensionBuildVersion -> ExtensionVersion const indirection - Remove #pragma warning disable for IDE0073; use correct file header directly - Remove per-extension BuildInfo.cs.template duplicates (7 files) - Remove SharedExtensionHelpers/ExtensionVersion.cs wrapper
…tal build, and test metadata stripping - Remove namespace declaration from SharedExtensionHelpers/BuildInfo.cs.template to align with existing templates (PlatformVersion, MSTestVersion, etc.) that use global namespace - Move BuildInfoTemplateFile default outside GenerateVersionSourceFile target for proper incremental evaluation and add template file to Inputs so template changes trigger regeneration - Strip +metadata from AssemblyInformationalVersion in tests since ExtensionVersion.DefaultSemVer comes from $(Version) (semver only)
…x for test infrastructure The test infrastructure project uses ExtensionVersion.DefaultSemVer to specify the Microsoft.Testing.Platform package version in generated test projects. Since the project lives under test/Utilities (not src/Platform), its VersionPrefix defaults to the MSTest version (4.3.0) instead of the platform version (2.3.0), causing NU1102 errors when tests try to resolve Microsoft.Testing.Platform 4.3.0-ci. Override VersionPrefix to TestingPlatformVersionPrefix so the generated version matches the actual platform package version.
Extensions were reporting
VersionviaMicrosoft.Testing.Platform.Helpers.AppVersion.DefaultSemVer(through IVT), which incorrectly ties extension version identity to the loaded MTP version. This breaks version accuracy when extension and platform versions differ.Version source correction (extension-local, not platform-local)
ExtensionVersionhelper linked into each affected extension assembly.<GenerateBuildInfo>true</GenerateBuildInfo>in each affected extension projectBuildInfo.cs.templatethat generates an extension-local version constant at build timeVersionproperties now resolve from generated extension build info (ExtensionBuildVersion.Version) instead ofAppVersion.DefaultSemVer.CrashDump forward-compatibility adjustment
InternalsVisibleTofromMicrosoft.Testing.PlatformtoMicrosoft.Testing.Extensions.CrashDump.Touched extension areas
Focused regression coverage
AppVersion.