We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As part of RestQA is to allow backend engineers to have an easy way to run performance test with their favorite tool.
Currently the users can generate test fixture for the following performance tool:
npm i -D @restqa/restqa
We would love to be able to choose another tool such as Vegeta
Yes
The text was updated successfully, but these errors were encountered:
Codebase to modify:
Sorry, something went wrong.
Hey, Did you notice we tagged this issue as good first issue, would you consider to contribute?
It's very simple:
_🙏_contribution
No branches or pull requests
👀 Background
As part of RestQA is to allow backend engineers to have an easy way to run performance test with their favorite tool.
✌️ What is the actual behavior?
Currently the users can generate test fixture for the following performance tool:
🕵️♀️ How to reproduce the current behavior?
npm i -D @restqa/restqa
🤞 What is the expected behavior?
We would love to be able to choose another tool such as Vegeta
😎 Proposed solution.
🙏 Would you be willing to submit a PR?
Yes
Code of Conduct
The text was updated successfully, but these errors were encountered: