Skip to content
This repository has been archived by the owner on Oct 31, 2023. It is now read-only.

golemcli binary should output a message when golemapp is not running #5201

Open
12 tasks
ghost opened this issue Feb 13, 2021 · 1 comment
Open
12 tasks

golemcli binary should output a message when golemapp is not running #5201

ghost opened this issue Feb 13, 2021 · 1 comment
Labels
P3 Severity-Low/Effort-hard

Comments

@ghost
Copy link

ghost commented Feb 13, 2021

Rationale

When first running and installing golem, an error message is an output that terms need to be accepted among other things. When trying to run the golemcli after exiting, it outputs an ambiguous error message that the host is unavailable (os error 111). This should include

Description

Functional specification

golemcli, the component which interacts with golemapp.

User Interface

The golemcli should output something like;
ERROR: Cannot connect to host. Is golemapp running?

Technical specification

If not already present, have golemcli check to see if golemapp is running. If not, output a more verbose error.

Dependencies

M/A

Sub-components

N/A

Blockers

N/A

Additional tests

N/A

QA

Ensure that golemcli can correctly detect if golemapp is running, and return an error message if not.

Test scenarios:

N/A

Base test process

QA limited to the single feature (in case of very trivial changes)

New feature tests

N/A

Positive Scenario 1

No error code is output.

Negative Scenario 1

An error message is output notify the user they need to start golemapp

Possible regressions

N/A

Progress

Development

  • Feature implemented
  • Feature unit/integration tests implemented

Dev QA

  • Basic tests by the developer pass
  • Unit tests pass
  • Golem integration tests pass
  • Concent integration tests pass
  • Concent acceptance tests pass

Please choose the priority label for QA. It is set to the lowest by default. To setup higher priority please change the label
P0 label is set for Severity-Critical/Effort-easy
P1 label is set for Severity-Critical/Effort-hard
P2 label is set for Severity-Low/ Effort-easy
P3 label is set for Severity-Low/Effort-hard

QA team

  • Base scenario passes
  • Additional test 1 passes...
  • ...

Issues encountered during QA

When adding an issue here, please update testing scenarios and QA progress above

  • link to issue...
  • ...
@ghost ghost added the P3 Severity-Low/Effort-hard label Feb 13, 2021
@ghost
Copy link
Author

ghost commented Feb 13, 2021

This is the first issue i've submitted on github so sorry if I've screwed it up :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P3 Severity-Low/Effort-hard
Projects
None yet
Development

No branches or pull requests

0 participants