zowe / zowe/zowe-client-python-sdk
Resolve flaky system tests
Open
Nobody has claimed this yet.
enhancement
priority-low
tech-debt
- Dominant language
- Python
- Stars
- 44
- Forks
- 38
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 1
Description
System tests all pass currently. However there are some flaky ones that could be made more reliable:
- Filenames used in workflow tests are not unique per-user, so tests may fail if multiple users run tests at the same time.
- z/FS Mount/Unmount tests don't always clean up after themselves - see #383
- TSO test expects READY message to come back in first response, but there may be system notifications that precede it
- Job tests do not check status of submitted jobs, so if jobs fail due to JCL errors they still pass
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 system test suite and locating the workflow, z/FS mount/unmount, TSO, and job test entry points named in the issue. Review #383 for the cleanup concern, then make the tests reliable for concurrent users, notifications before READY, cleanup, and failed jobs; rerun the affected system tests to confirm they detect the intended conditions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100