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
Every [Something]Factory class that we have often contains a single method createSomething. We can turn the Factory Pattern into the Factory Method Pattern.
These createSomething static methods can be moved into the base abstract classes/interfaces (e.g., in this case we can place createTestBodyPrinter() static method into TestBodyPrinter interface (and maybe rename to just create()). This will allow us to remove a single entity from the codebase, namely TestBodyPrinterFactory. It'll reduce the code complexity.
In TestBodyPrinterFactory, TestCompilerFactory and TestSuiteParserFactory
The text was updated successfully, but these errors were encountered:
Some of this factories are used not only on one class.
For example, TestCompilerFactory is used in TestSparkStarter, TestCasePanelFactory and in LLMProcessManager, therefore we need to have an extra entity for it.
For other classes it could happen that we will need them in other places as well, so having the Factory abstraction is crucial
Description
More description is in the PR comment.
In
TestBodyPrinterFactory
,TestCompilerFactory
andTestSuiteParserFactory
The text was updated successfully, but these errors were encountered: