Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improving tests env #65

Open
smallhive opened this issue May 27, 2024 · 0 comments
Open

Improving tests env #65

smallhive opened this issue May 27, 2024 · 0 comments
Labels
enhancement Improving existing functionality I2 Regular impact S2 Regular significance U3 Regular

Comments

@smallhive
Copy link

Is your feature request related to a problem? Please describe.

A new tests run env is good and it can be better after some quality of live updates.

Describe the solution you'd like

As a developer I need options to use my own s3-gate. Just replace a separate binary file is good but if I need to replace gate file I have to restart all env. This way is not suggesting a way to propper debug routine.
The best solution is generating the complete s3 gate config file. I mean I would use this file as a parameter to the gate --config /some/path/to/config.yaml
Right now I tried to use configuration file, but was failed. Some parameters, like node-peears are set via env params and I can't find them.

Running tests generate tons of rows. It is difficult to find info. We may group all useful data (paths to configs, to logs, etc) in one place or maybe use green or any colour to highlight it in logs.

Describe alternatives you've considered

Improve test logging and make them configurable in some way. Reducing logs may be also good option

Additional context

Right now maybe not very actual, but the same would be useful for the REST gate as well.

@smallhive smallhive added enhancement Improving existing functionality I2 Regular impact feature Completely new functionality labels May 27, 2024
@roman-khimov roman-khimov added U3 Regular S2 Regular significance and removed feature Completely new functionality labels May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improving existing functionality I2 Regular impact S2 Regular significance U3 Regular
Projects
None yet
Development

No branches or pull requests

3 participants