redhat-developer / redhat-developer/vscode-openshift-tools
Find a way to make sure component is present for UI tests
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 123
- Forks
- 63
- Avg merge
- 6h 16m
- Merged PRs (30d)
- 74
Description
Some UI tests depend on a component to be present. Right now, if the component is not present, the tests are skipped and don't give any meaningful result. By finding a way to make sure component is present, we can run these tests even if "Create component" tests fail.
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 locating the UI tests and the “Create component” tests in the VS Code extension test suite, then trace how missing components currently cause tests to be skipped. Done means the dependent tests still run when component creation fails and report a meaningful result instead of being silently skipped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100