redhat-developer / redhat-developer/rsp-server-community

Implement itests for start/restart/stop server operation

Open
#172 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

tests
Dominant language
Java
Stars
39
Forks
20
Avg merge
2h 26m
Merged PRs (30d)
4

Description

  1. Start the server : Select server -> context menu -> start server -> verify that the server has started (for example localhost:8080 and console output "Server startup in [618] milliseconds")
  2. Restart the server: Start the server -> context menu -> Restart in Run mode-> verify that server has started
  3. Stop the server: Start the server -> context menu -> Stop server -> verify server has stopped

More info: https://docs.google.com/spreadsheets/d/1P9dz739aKqsuVajwPbiFtkdm4HDKZddBa7XjzMpFtE4/edit#gid=0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or existing test is named. Start by locating the repository's integration-test setup and server lifecycle entry points, then review the linked spreadsheet for expected scenarios. Done means automated coverage verifies start, restart in Run mode, and stop behavior, including the stated startup and stopped-server checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, testing
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.