-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Added The return of Post Value when an Integration Exception is thrown while Save Action #26660
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
Added The return of Post Value when an Integration Exception is thrown while Save Action #26660
Conversation
This keeps the form data persistent when the an Integration Exception is throw as a case when name of Integration being added is same.
Hi @realadityayadav. Thank you for your contribution
For more details, please, review the Magento Contributor Guide documentation. |
@realadityayadav unfortunately, only members of the maintainers team are allowed to assign developers to the pull request |
@magento give me test instance |
Hi @realadityayadav. Thank you for your request. I'm working on Magento instance for you |
Hi @realadityayadav, here is your new Magento instance. |
Hi @realadityayadav. Thank you for your collaboration. Thank you! |
Ya why not. Could you guide me to a reference of adding an MFTF please? |
Probably the last step verifying the form fields should be added to this test: https://github.com/magento/magento2/blob/2.4-develop/app/code/Magento/Integration/Test/Mftf/Test/AdminCreateIntegrationEntityWithDuplicatedNameTest.xml |
@rogyar The Test are failing for a different module in the EE & B2B files which are not yet available in this release? |
@@ -46,5 +46,6 @@ | |||
<argument name="message" value="The integration with name "Integration1" exists."/> | |||
<argument value="error" name="messageType"/> | |||
</actionGroup> | |||
<seeInField stepKey="checkEnteredValueIsPreserved" selector="{{AdminNewIntegrationSection.name}}" userInput="Integration1"/> |
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.
Hi @realadityayadav. According to the best practices it's highly recommended to build a test using action groups without direct operations in the test body. As you can see from the test you have edited, it consists of the action groups.
Please, move this check into a new action group and name the action group as AssertAdminIntegrationNameInFormActionGroup
. Then you can use the action group in your test.
Thank you!
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.
https://github.com/magento/magento2/pull/26660/files
Please see the recent change now @rogyar
Hi @realadityayadav. Looks like you forgot to create the mentioned action group. According to my previous comment you need to perform the following steps.
As far as I see, steps 1-2 are missing so far. |
I think it is already there. Please check the latest version. |
Hi @realadityayadav. You have 2 files modified in your PR: the actual fix and the test. No action group so far. |
@magento create issue |
@magento run WebAPI tests |
@magento run WebAPI Tests |
@magento run Integration Tests |
…tion is thrown while Save Action #26660
Hi @realadityayadav, thank you for your contribution! |
This keeps the form data persistent when the an Integration Exception is throw as a case when name of Integration being added is same.
Description (*)
Magento 2.x - This issue reproduce in all version.
Go to System-> Integrations
Add a new Integration , Choose a name that already exist and fill all the form and then hit Save.
Expected - The Save Actions Fails with a message The integration with name "%1" exists. but the form entries are intact.
Actual - The Save Actions Fails with a message The integration with name "%1" exists. but the form entries are reset.
Related Pull Requests
Fixed Issues (if relevant)
Manual testing scenarios (*)
Questions or comments
Contribution checklist (*)
Resolved issues: