OliverOdo
OliverOdo
Thanks @dycops!
@cristianrgreco I'm not sure you could support us on that issue 🙏
Draft from the weekly catchup with @KaTLaz and @samuxdesign. We discuss about the dependencies between Features and Scenarios: * A user can create X features * 1 feature can contains....
As discussed during the last call, one of the challenge is: - As RestQA we do not know what will be the fields available on the API, QA will need...
A scenario example:  The scenario is testing an api with the following specs: | URL | Method | Fields | Response status code | Response body | | ----...
Codebase to modify: * https://github.com/restqa/restqa/blob/master/packages/core-performance/src/vendors/index.js * https://github.com/restqa/restqa/blob/master/packages/core-performance/src/vendors/vegeta.js
Converting this PR as draft since it's required more work on the following: * Delete dead link * Remove or ignore link with ssl issues * Manage the rate limit...
In order to reproduce the error: 1. create an error: replace the `program` by `progra` on the line https://github.com/restqa/restqa/blob/master/packages/cli/bin/restqa.js#L15 2. run `cd packages/cli && npm run build` 3. run `DEBUG=restqa...
So far the remaining work on this PR is: * A few links that need to be remove, * Swagger.io needs to be added to the whitelist. If you are...
@withshubh Thank you for the feedback, i rebased and changed the order. 🙏