Test-More / Test-More/Test2-Harness
New "test info" file requires that the current directory be writable
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 28
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
The recently added "test info" file (see https://github.com/Test-More/Test2-Harness/blob/32e0ca1bd892a13614f3e0c4a090762e34c0c177/lib/App/Yath/Command/test.pm#L263), used for yath resources, requires that Yath be run from a directory which is writable. When running builds/tests inside of a Docker Container, though, this may not always be the case.
Should this file not be recorded into a temp directory (such as /tmp) instead?
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 with lib/App/Yath/Command/test.pm around line 263 and trace how the “test info” file is created for yath resources. Check the behavior when Yath runs from a non-writable directory, including in a container. Done means the command no longer requires the current directory to be writable and the file is recorded in an appropriate temporary location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- cli, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100