redhat-developer / redhat-developer/rsp-server-community
[Epic] Introduce e2e UI test to cover the most used server runtimes
Open
Nobody has claimed this yet.
kind/epic
tests
- Dominant language
- Java
- Stars
- 39
- Forks
- 20
- Avg merge
- 2h 26m
- Merged PRs (30d)
- 4
Description
Introduce basic UI tests coverage and get inspired in [1].
- Define most used and valuable servers to test
- Figure out if they share the same functionality (does everyone supports deploy? - for future extension of the testing)
- Introduce the testing into CI (github actions)
Epic issue for:
- #214
- #215
- #216
For more info: https://docs.google.com/spreadsheets/d/1P9dz739aKqsuVajwPbiFtkdm4HDKZddBa7XjzMpFtE4/edit#gid=0
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
Read the referenced basicServerTest.ts example first, then review child issues #214, #215, and #216 to identify the proposed runtime coverage. Define the selected servers and shared behavior, add the e2e UI tests, and integrate them into GitHub Actions so the runtime checks execute in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, java
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100