manage-fake

Test fakes for TypeScript interfaces are generated by providing the interface name, which auto-creates a Fake class, an Initializer, and a Builder under the fakes folder following existing project patterns. This includes support for interfaces extending IEntity and EventBrokers.

Yes, existing fake test doubles can be updated when a TypeScript interface changes. The process adds or removes fields and methods as needed, ensuring the Fake class, Initializer, and Builder stay aligned with the latest interface definitions without requiring a full rewrite.

Using the generated Builder is the best way to set up default mock values for TypeScript entity tests. The Builder provides sensible defaults for initialization, allowing you to customize values before instantiation to streamline your testing setup.

Yes, the fake builder pattern supports EventBrokers and related types in TypeScript. The generation process targets interfaces and produces a cohesive Fake class, Initializer, and Builder that integrate with EventBrokers following the project's existing patterns.

Generated initializers require mandatory fields for TypeScript fakes to enforce safe instantiation and ensure critical properties are explicitly provided. This standardized pattern uses getMockingFunction for method stubs and a dedicated ReturnValue slot for method returns.

A fakes/index.ts export file is needed to properly export TypeScript mock classes and builders. The skill automatically updates or creates this index file to maintain cohesive imports across your testing infrastructure when generating or updating fakes.