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
The use of the ClassInitializer mechanism to initialize a dependency injection framework leads to the context being initialized multiple times even within a given specification. Is there a way to perform this initialization more globally, so that the context can be shared? This would help to avoid the performance penalty of initialization, among other potential benefits. Having something like a SuiteInitializer or SpecificationInitializer, would help to provide more control over this process. My initial need is to initialize the context once, but more granular control would be welcomed as well.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The use of the ClassInitializer mechanism to initialize a dependency injection framework leads to the context being initialized multiple times even within a given specification. Is there a way to perform this initialization more globally, so that the context can be shared? This would help to avoid the performance penalty of initialization, among other potential benefits. Having something like a SuiteInitializer or SpecificationInitializer, would help to provide more control over this process. My initial need is to initialize the context once, but more granular control would be welcomed as well.
Beta Was this translation helpful? Give feedback.
All reactions