zowe / zowe/zowe-client-python-sdk
[tests]: Generate dynamic names to make integration/system tests more reliable
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44
- Forks
- 38
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 1
Description
Is your feature or enhancement request related to a problem or limitation? Please describe
Today, we use static fixtures for the data used when creating datasets, USS files, and submitting jobs.
Describe your enhancement idea
Ideally we would generate pseudo-random names for content created on the mainframe for the purpose of system testing.
Describe alternatives you've considered
Keep using static content 😢
Provide any additional context
This might serve as an example:
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 reviewing the system tests that create datasets, USS files, and submit jobs, then compare their static fixtures with the referenced zowe-cli example at packages/cli/tests/zosuss/system/issue/cli.issue.ssh.system.test.ts. The work is done when test-created mainframe content uses pseudo-random names and the integration/system tests remain reliable without static-name collisions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100