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

Quite like the tool, some feedback for next version #16

Open
JesseAbram opened this issue Nov 3, 2020 · 1 comment
Open

Quite like the tool, some feedback for next version #16

JesseAbram opened this issue Nov 3, 2020 · 1 comment

Comments

@JesseAbram
Copy link

This is a great tool, what I have and a few other teams I have been talking to are looking for. For next version Id love to suggest some possible improvements/extra features

  1. More examples and documentation, I have started to set up this repo, and can hopefully add more generalized tests and it can be used as examples for other teams

  2. A before each hook that resets the state of the dev chain (I know this is hard and will probably require an RPC call on the substrate side, but worthwhile to look into)

  3. Access to more features of Polkadot JS. When trying to call random RPC calls like account next nonce and signing with a different nonce (to bombard the node with tx) see here I had to manually pull in the polkadot js api.

  4. An option to store results in a postgres DB for later use (optional, maybe not the best idea, but worth thinking about)

  5. Documentation to set this up with Grafana

  6. A call that load tests a chain and can give some sort of printout to an approx tps and if it is good or bad. As well to set failures on min tps for a specific call so it can be run in a pipeline

@ByKeks
Copy link
Member

ByKeks commented Nov 4, 2020

Thanks for your feedback!

  1. We have a repo with an example project https://github.com/halva-suite/halva-test-example, we welcome contributions ;)

  2. Yes, it's a very useful feature, but - as you rightly note - this is hard for development. But we thinking about it and have some ideas

  3. I need some times to research this question, maybe it's will be done soon

  4. It is my opinion that the responsibility is not for this tool, you can do it manually. Some people don't need to save results to a DB or may want to use a different DB instead of Postgres.

  5. Ok, I get it

  6. Yes, It's a good idea

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants