メニュー
Validate legacy repository seams by exercising real gateway stubs and DataSet mapping in NUnit.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
| name | legacy-dal-repository-tests |
| description | Validate legacy repository seams by exercising real gateway stubs and DataSet mapping in NUnit. |
| domain | testing |
| confidence | high |
| source | earned |
Use this when the repo already has a fake legacy gateway (LegacyDbGateway) that returns DataSet stubs and you need believable DAL coverage without mocking frameworks.
Tests.Unit\Repositories\{Area}\...Fixture.cs so repository mapping stays separate from service tests.Repositories\StoreOps\DispatchTicketRepositoryFixture.csRepositories\CustomerHub\PartnerAccountRepositoryFixture.csRepositories\Reporting\WorkforceReportRepositoryFixture.csDataSet table names, or row-shape assumptions.999, which should stay observable for regression checks.