-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MFTF-33305: Eliminate AspectMock from ObjectExtensionUtilTest #843
MFTF-33305: Eliminate AspectMock from ObjectExtensionUtilTest #843
Conversation
*/ | ||
public function setUp(): void | ||
protected function setUp(): void | ||
{ | ||
TestLoggingUtil::getInstance()->setMockLoggingUtil(); | ||
$resolverMock = new MockModuleResolverBuilder(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @bohdan-harniuk
Thank you for contribution.
Your changes look good for me.
Hello, @jilu1 In this task, we don't have any new singletons created. Please, proceed with the code review! Thanks, Bohdan |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @bohdan-harniuk
Thank you for your contribution.
The changes look well for me.
@magento import pull request to https://github.com/magento-commerce/magento2-functional-testing-framework |
@jilu1 the pull request successfully imported. |
Description
Eliminated AspectMock usage in the \tests\unit\Magento\FunctionalTestFramework\Test\Util\ObjectExtensionUtilTest.
Fixed Issues (if relevant)
Additional information
As the main idea of this issue to eliminate AspectMock usage in the ObjectExtensionUtilTest class, AspectMock usage eliminated only partially in the MockModuleResolverBuilder. It is a required action because in that class the \Magento\FunctionalTestingFramework\Util\ModuleResolver mocked instance hardcoded to be retrieved by the ObjectManager mocked object on its create method without any argument.
Contribution checklist