magento / magento/community-features
Community Lead / Maintained Unit Testing on github pull request
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 46
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Hey Guys,
I'd love to start a small community group that maintains the unit testing for Magento 2, and enforces that on github merges.
My company https://storebase.io/ is seeing a huge amount of Magento 2 github issues that don't get resolved or get pushed to the backburner, and many many of them, would be easily resolved with unit testing.
Would love to gauge support for this, and see what contributions everyone would be willing to give. My company could commit around 1hr a week to start with to get this kicked off, but we'd need support from Magento Core Team to get the unit tests as part of the github merge process.
Thanks,
Tony Schirmer
Contributor guide
No contributing guide indexed for this repository
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 reviewing Magento 2's current unit-testing practices and the GitHub merge process mentioned in the proposal. Determine what community support and Magento Core Team agreement would be required; the work is done only when the ownership model and merge enforcement plan are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100