Revise ext/standard/tests/file test suite
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 40.4k
- Forks
- 8.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 96
Description
Description
Occasionally, there are still test conflicts, and a couple of tests are marked as obscure_filename conflicting. Furthermore, some of the tests do not necessarily clean up properly after execution (they unlink some created files during test execution only). Also, some tests appear to have POSIX and Windows variants, although that doesn't seem to be necessary. See e.g. #16722 and #16854.
Ideally, all tests should only create and delete files which either have the same base name as the test case, or are placed in a directory with the base name of the test case. Since this may lead to overlong paths, we may need to take some shortcuts there (possibly using shorter test case names).
In any way, this test suite should be cleaned up/improved.
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
Review ext/standard/tests/file and the related examples in #16722 and #16854 first. Inventory the conflicts, obscure_filename markings, cleanup behavior, and POSIX/Windows variants; done means the suite consistently isolates its files or directories and removes created files without unnecessary variants.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100