Menu
Lock legacy gateway, host, and batch-job outputs with sparse NUnit smoke coverage before DI refactors land.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | legacy-host-smoke-baseline |
| description | Lock legacy gateway, host, and batch-job outputs with sparse NUnit smoke coverage before DI refactors land. |
| domain | testing |
| confidence | high |
| source | earned |
Use this when a legacy modernization issue is about wiring or composition, but the implementation has not landed yet. Tester-owned progress should protect the observable seams that a refactor must preserve rather than speculating on the future container API.
src\before\Fabrikam.EnterprisePizza.Legacy.Tests with thin, believable smoke tests instead of broad end-to-end coverage.Count > 0 when the sample already has stable seeded rows.dotnet msbuild <project> /t:Restore /p:RestorePackagesConfig=true and point nunit.framework at %UserProfile%\.nuget\packages if no repo-local packages\ folder exists.src\before\Fabrikam.EnterprisePizza.Legacy.Tests\SmokeTests\LegacyDbGatewayFixture.cssrc\before\Fabrikam.EnterprisePizza.Legacy.Tests\SmokeTests\NightlyPosImportJobFixture.cssrc\before\Fabrikam.EnterprisePizza.Legacy.Tests\SmokeTests\StoreDispatchServiceFixture.cssrc\before\Fabrikam.EnterprisePizza.Legacy.Tests\SmokeTests\PartnerSyncServiceFixture.cssrc\before\packages\ folder when the worktree restores NUnit into the user NuGet cache.Squad branching model: main-only workflow with feature branches
{what this skill teaches agents}
Wire legacy .NET Framework service hosts through Enterprise Library-flavored appSettings so Unity, service location, exception policies, logging, and database aliases all hang off one configuration seam.
Build internal order-management Web Forms pages with ObjectDataSource, GridView, DetailsView, and ViewState-heavy filter handling.
Build a believable mid-2000s .NET data layer around connection catalogs, stored-procedure wrappers, DataSets, and repository facades.
Anchor store-ops workbench screens in separate StoreOps tables for order state, status snapshots, workforce alerts, and zone bulletins, with dispatch tickets linked back to orders.