apex-migration

To migrate NuGet PowerShell E2E tests to C# Apex, you translate Install-PackageTest or Update-PackageTest functions into the Apex test layout while preserving the exact scenario and assertions. This process routes PMC, UI, and sync scenarios to the appropriate Apex test file.

Converting PowerShell PMC command execution patterns to Apex tests requires mapping project-template factories and PMC command execution semantics to their closest Apex equivalents. This ensures your test suite becomes faster, more consistent, and easier to maintain.

Yes, you can preserve NuGet.config setup and assertions when porting PowerShell tests to C#. The migration process includes deterministic translation rules that convert package source setup and NuGet.config manipulation into matching Apex test equivalents.

You should not migrate a PowerShell E2E test to Apex when existing Apex coverage already exists for that scenario. The migration process includes safety guardrails to advise skipping duplicate-covered scenarios and avoiding duplicate gating.

Yes, NuGet Apex migration supports binding redirect and audit scenarios. The workflow correctly routes these specific interaction surfaces, alongside IVs and .NET project-creation scenarios, into the appropriate Apex test files during translation.

The apex-migration skill handles test suite cleanup by verifying compilation of the newly translated C# Apex test and then removing the original PowerShell E2E test function to prevent duplicate coverage and streamline maintenance.