Document inner workings of PrestaShop phpunit test suite
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 136
- Forks
- 555
- Avg merge
- 4d 14h
- Merged PRs (30d)
- 4
Description
Although we rely on a very standard technology (phpunit) for our unit tests, we have built specific helpers / conventions / systems / utils to test PrestaShop that fit the project specific needs. We have helpers to mock legacy classes, we have reset database utilities, we have util classes to reboot the kernel ...
We should document them (how they work, why they were introduced, how to use them) to help newcomers extend the test suite.
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 inventorying the PHPUnit helpers, conventions, legacy-class mocking, database reset utilities, and kernel reboot utilities described in the issue. Document how each works, why it exists, and how newcomers should use it when extending the PrestaShop test suite.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- documentation, testing-qa
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100