zopencommunity / zopencommunity/bashport
General issue to track failing tests in bash test suite
Open
Nobody has claimed this yet.
help wanted
- Dominant language
- Groovy
- Stars
- 12
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Many tests are failing because there is a discrepancy in the error messages:
EDC5129I No such file or directory
vs
No such file or directory
We may need to create a platform specific *.right file for some tests
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 running the bash test suite and identify which failures differ only in their error-message text, especially the EDC5129I prefix. Review the affected expected-output files and determine where platform-specific *.right files are needed. Done means the relevant tests use the correct expected messages and pass on the target platform.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, shell
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100