القائمة
Model legacy cross-system workflows with passing seam checks plus explicit pending scenarios
التثبيت باستخدام 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-integration-stub-fixtures |
| description | Model legacy cross-system workflows with passing seam checks plus explicit pending scenarios |
| domain | testing |
| confidence | high |
| source | earned |
Use this when a legacy .NET Framework solution needs believable integration coverage, but the workflow still terminates in brittle UI code-behind, SOAP hosts, or console entry points that do not justify a full harness in the current issue.
ProjectReference entries for every assembly whose public types appear in the stub fixture.Explicit and end them with Assert.Inconclusive(...) that names the blocker and the exact file or seam still preventing full execution.src\before\Fabrikam.EnterprisePizza.Legacy.Tests\IntegrationStubs\CrossSystemWorkflowStubFixture.cssrc\before\Fabrikam.EnterprisePizza.Legacy.Tests\IntegrationStubs\ScenarioStub.cs