magento / magento/catalog-storefront
[TEST] Automate log-exception check mechanism for storefront integration tests
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 7
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
We do have manual check of exception log as one the Code Review steps.
We can automate it to accelerate the Review phase.
We Could create the NoExcept abstract class for tests and inherit it for all of the tests that shouldn't throw any exception. As part of the functionality of this parent class would be the substitution of LogInterface instance and verification the corresponding log file on the existence of exception after the test completed (TearDown phase).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the storefront integration tests and reviewing the current manual exception-log check used during code review. Define how the NoExcept abstract test class, LogInterface substitution, and teardown verification should apply to tests that must not throw exceptions; done means those tests automatically detect the corresponding exception log without manual review.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100