legacy-integration-stub-fixtures

스타0

포크0

업데이트2026년 5월 14일 14:26

Model legacy cross-system workflows with passing seam checks plus explicit pending scenarios

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

jongalloway

jongalloway/EnterpriseModernizationSample

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Context

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.

Patterns

Keep the work inside the existing legacy NUnit project instead of spinning up a brand-new test stack.
Add direct ProjectReference entries for every assembly whose public types appear in the stub fixture.
Prefer passing seam checks for flows that already compose in code, such as service-to-business or job-to-gateway wiring.
Mark broader end-to-end placeholders as Explicit and end them with Assert.Inconclusive(...) that names the blocker and the exact file or seam still preventing full execution.

Examples

src\before\Fabrikam.EnterprisePizza.Legacy.Tests\IntegrationStubs\CrossSystemWorkflowStubFixture.cs
src\before\Fabrikam.EnterprisePizza.Legacy.Tests\IntegrationStubs\ScenarioStub.cs

Anti-Patterns

Writing failing placeholder tests into the default run path.
Hiding blockers in vague TODO comments instead of naming the missing seam.
Turning a test-stub issue into a UI refactor just to make an end-to-end case runnable.

이 저장소의 다른 Skills

같은 저장소

git-workflow

jongalloway/EnterpriseModernizationSample

Squad branching model: main-only workflow with feature branches

2026-05-180

skill-name

jongalloway/EnterpriseModernizationSample

{what this skill teaches agents}

2026-05-180

legacy-entlib-runtime-bootstrap

jongalloway/EnterpriseModernizationSample

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.

2026-05-180

legacy-webforms-order-binder

jongalloway/EnterpriseModernizationSample

Build internal order-management Web Forms pages with ObjectDataSource, GridView, DetailsView, and ViewState-heavy filter handling.

2026-05-180

legacy-dal-seam

jongalloway/EnterpriseModernizationSample

Build a believable mid-2000s .NET data layer around connection catalogs, stored-procedure wrappers, DataSets, and repository facades.

2026-05-150

legacy-storeops-workbench-schema

jongalloway/EnterpriseModernizationSample

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.

2026-05-150

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

Context

Patterns

Keep the work inside the existing legacy NUnit project instead of spinning up a brand-new test stack.
Add direct ProjectReference entries for every assembly whose public types appear in the stub fixture.
Prefer passing seam checks for flows that already compose in code, such as service-to-business or job-to-gateway wiring.
Mark broader end-to-end placeholders as Explicit and end them with Assert.Inconclusive(...) that names the blocker and the exact file or seam still preventing full execution.

Examples

src\before\Fabrikam.EnterprisePizza.Legacy.Tests\IntegrationStubs\CrossSystemWorkflowStubFixture.cs
src\before\Fabrikam.EnterprisePizza.Legacy.Tests\IntegrationStubs\ScenarioStub.cs

Anti-Patterns

Writing failing placeholder tests into the default run path.
Hiding blockers in vague TODO comments instead of naming the missing seam.
Turning a test-stub issue into a UI refactor just to make an end-to-end case runnable.