magento2
magento2 copied to clipboard
Correct typo and grammar in acl.xsd file
Description (*)
This pull request corrects typo and incorrect grammar in the lib/internal/Magento/Framework/Acl/etc/acl.xsd file.
Related Pull Requests
This pull request changes only documentation strings and does not alter Magento behaviour. Therefore there is no special testing is required other than confirming that the previous typo/grammar was wrong, and the current grammar is correct.
Fixed Issues (if relevant)
N/A
Manual testing scenarios (*)
N/A
Questions or comments
N/A
Contribution checklist (*)
- [ ] Pull request has a meaningful description of its purpose
- [ ] All commits are accompanied by meaningful commit messages
- [ ] All new or changed code is covered with unit/integration tests (if applicable)
- [ ] README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
- [ ] All automated tests passed successfully (all builds are green)
Resolved issues:
- [x] resolves magento/magento2#38061: Correct typo and grammar in acl.xsd file
Hi @mage2pratik. Thank you for your contribution! Here are some useful tips on how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:
@magento give me test instance- deploy test instance based on PR changes@magento give me 2.4-develop instance- deploy vanilla Magento instance
:exclamation: Automated tests can be triggered manually with an appropriate comment:
@magento run all tests- run or re-run all required tests against the PR changes@magento run <test-build(s)>- run or re-run specific test build(s) For example:@magento run Unit Tests
<test-build(s)> is a comma-separated list of build names.
Allowed build names are:
Database CompareFunctional Tests CEFunctional Tests EEFunctional Tests B2BIntegration TestsMagento Health IndexSample Data Tests CESample Data Tests EESample Data Tests B2BStatic TestsUnit TestsWebAPI TestsSemantic Version Checker
You can find more information about the builds here :information_source: Run only required test builds during development. Run all test builds before sending your pull request for review.
For more details, review the Code Contributions documentation. Join Magento Community Engineering Slack and ask your questions in #github channel.
@magento create issue
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.
@magento run all tests
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.
✔️ QA Passed
Preconditions:
Install fresh Magento 2.4-develop
Manual testing scenario:
- Go to lib/internal/Magento/Framework/Acl/etc/acl.xsd
- Verify the acl.xsd
- Item id attribute can have only [a-z0-9/_]. Minimal length 3 symbol. Case insensitive
Before: ✖️
After: ✔️
Builds are failed. Hence, moving this PR to Extended Testing.
@magento run all tests
@magento run Functional Tests B2B ,Functional Tests EE ,Functional Tests CE
Functional Tests EE,Functional Tests CE,Functional Tests B2B tests failure are different on last two run on same commit. And Also it contains some known failures. List of known failures. ACQE-6774 ACQE-6695 ACQE-6331 ACQE-6786 ACQE-6469
Functional Tests EE
Run1
Run2
Functional Tests CE
Run1
Run2
Functional Tests B2B
Run1
Run2
Hence moving it to merge in progress