You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
vs-mef works well for testing applications, but it can be difficult to create and manage IExportProviderFactory instances that provide ideal behavior for testing. dotnet/roslyn has been iterating on this concept, and currently uses the following two types as the core of the testing functionality:
TestComposition: Assists in caching IExportProviderFactory instances for equivalent compositions
ExportProviderCache: Ensures that only one ExportProvider is created in the context of a given test
UseExportProviderAttribute: Ensures that an ExportProvider created by one test is not reused outside the context of that test
It may be worth building a library with tools to assist other application developers write tests with one or more of these concepts.
The text was updated successfully, but these errors were encountered:
AArnott
pushed a commit
to AArnott/vs-mef
that referenced
this issue
Dec 1, 2022
vs-mef works well for testing applications, but it can be difficult to create and manage
IExportProviderFactory
instances that provide ideal behavior for testing. dotnet/roslyn has been iterating on this concept, and currently uses the following two types as the core of the testing functionality:TestComposition
: Assists in cachingIExportProviderFactory
instances for equivalent compositionsExportProviderCache
: Ensures that only oneExportProvider
is created in the context of a given testUseExportProviderAttribute
: Ensures that anExportProvider
created by one test is not reused outside the context of that testIt may be worth building a library with tools to assist other application developers write tests with one or more of these concepts.
The text was updated successfully, but these errors were encountered: