Migrate NetCore E2E tests from PowerShell to Apex#7246
Conversation
test/NuGet.Tests.Apex/NuGet.Tests.Apex/NuGetEndToEndTests/NetCoreProjectTestCase.cs
Outdated
Show resolved
Hide resolved
test/NuGet.Tests.Apex/NuGet.Tests.Apex/NuGetEndToEndTests/NetCoreProjectTestCase.cs
Outdated
Show resolved
Hide resolved
|
There are some build failures in https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=13714875&view=logs&j=3dc8fd7e-4368-5a92-293e-d53cefc8c4b3&t=28a433a8-2ece-5e8d-89c3-cb5517da6c35.
|
Added missing |
|
@copilot Rebase on top of dev. |
I've rebased locally on top of |
0ba7c44 to
5a68ca1
Compare
|
Rebased |
test/NuGet.Tests.Apex/NuGet.Tests.Apex/NuGetEndToEndTests/NetCoreProjectTestCase.cs
Outdated
Show resolved
Hide resolved
a47fd5b to
ad4945f
Compare
|
@copilot NetCoreMultipleTargetFrameworksVSandMSBuildNoOp is not covered by NetCoreVSAndMSBuildRestoreIsNoOp They are testing different scenarios since NetCoreMultipleTargetFrameworksVSandMSBuildNoOp is talking about a multi targeted project. Fix that. |
… multi-targeted projects Agent-Logs-Url: https://github.com/NuGet/NuGet.Client/sessions/247a9488-be33-43c9-9494-fadabefae6c8 Co-authored-by: nkolev92 <2878341+nkolev92@users.noreply.github.com>
Added |
test/NuGet.Tests.Apex/NuGet.Tests.Apex/NuGetEndToEndTests/NetCoreProjectTestCase.cs
Outdated
Show resolved
Hide resolved
Agent-Logs-Url: https://github.com/NuGet/NuGet.Client/sessions/c6cec734-7d92-4cd2-a819-9e05ed4bbacb Co-authored-by: nkolev92 <2878341+nkolev92@users.noreply.github.com>
test/NuGet.Tests.Apex/NuGet.Tests.Apex/Utility/CommonUtility.cs
Outdated
Show resolved
Hide resolved
… not set Agent-Logs-Url: https://github.com/NuGet/NuGet.Client/sessions/15d710ba-13f6-41e5-a73f-6e176e99e050 Co-authored-by: nkolev92 <2878341+nkolev92@users.noreply.github.com>
…Process Agent-Logs-Url: https://github.com/NuGet/NuGet.Client/sessions/bd72d893-c297-47bb-b3f9-2b12de5c0b60 Co-authored-by: nkolev92 <2878341+nkolev92@users.noreply.github.com>
The VS-vs-MSBuild no-op tests require that both VS internal restore and external MSBuild.exe use the same NuGet assemblies. Apex deploys the dev VSIX only to the experimental instance hive, but MSBuild.exe at <VSRoot>/MSBuild/Current/bin/ still uses the shipped NuGet code. This version mismatch causes the no-op assertion to fail, so these tests must remain as PS E2E tests where the VSIX is fully installed. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Progress: https://github.com/NuGet/Client.Engineering/issues/2085
Description
Migrate and clean up PowerShell E2E tests from
test/EndToEnd/tests/. Some tests are migrated to Apex, some are deleted as duplicates of existing Apex tests, some are deleted as obsolete, and some are kept as PS because they cannot work correctly in the Apex experimental-instance environment.Note - This does not mean, at this point, we are unable to migrate all of our tests to Apex. We need to figure out a workaround to test these scenarios, as cross tool no-op is a critical performance feature.
Test migration table
NetCoreProjectTest.ps1Test-NetCoreProjectSystemCacheUpdateEventISolutionManagerevent subscription not feasible in ApexTest-NetCoreConsoleAppCleanVerifyCacheFileInsideObjFolderin Apex Daily (NuGetConsoleTestCase.cs)Test-NetCoreConsoleAppRebuildDoesNotDeleteCacheFileVerifyCacheFileInsideObjFolderin Apex Daily (NuGetConsoleTestCase.cs)Test-NetCoreVSandMSBuildNoOpMSBuild.exestill uses shipped NuGet assemblies, causing version mismatch that breaks no-op assertionTest-NetCoreTargetFrameworksVSandMSBuildNoOpTest-NetCoreMultipleTargetFrameworksVSandMSBuildNoOpTest-NetCoreToolsVSandMSBuildNoOpServicesTest.ps1Test-MigrateVanillaUwpProjectJsonToPackageReferenceOther changes
PackageReferenceClassLibraryandPackageReferenceClassLibraryWithLockFileE2E project templatesPR Checklist