viktor-svirsky / swagger2locustio Goto Github PK

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

--swagger-file SWAGGER_FILE
path to swagger file (default: None)
--results-path RESULTS_PATH
path to store locustfile.py (default: generated)
--loglevel {info,debug,warning,error}
logging level (default: info)
--strict-level {0,1,2}
add paths with required params without default values
to locust tests (default: 2)
--operations {get,post,put,patch,delete,head,options,trace} [{get,post,put,patch,delete,head,options,trace} ...]
operations to use in api testing (default: ['get'])
--paths-white PATHS_WHITE [PATHS_WHITE ...]
paths to use in api testing (default: [])
--paths-black PATHS_BLACK [PATHS_BLACK ...]
paths not to use in api testing (default: [])
--tags-white TAGS_WHITE [TAGS_WHITE ...]
tags to use in api testing (default: [])
--tags-black TAGS_BLACK [TAGS_BLACK ...]
tags to use in api testing (default: [])

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Params without a default value, or examples

Descriptions
Almost all API specs have a lot of params without default values (required and not required).

Solution
It would be great to create the file with helper functions (or classes) that will help to generate those values (for example function, that returns random int) and attach that file to the generated locustio file.

Problems
There can also be params without param_type specified so we need to consider how we'll deal with those situations.

Alternatives
The straightforward solution is to generate an additional file that will contain all params without values so people need to add values themself.

Coveralls provides a history of code coverage.
On https://coveralls.io/ signup using your GitHub credentials

With a bigger swagger files I need to divide locust files into the folders.

1. Please create hierarchical folder structure for endpoints that have more than 2 members. Ex:
   /v1/alpha
   /v1/beta
   /v2
   => /v1 - locust, and root locust

2. Add parameter to disable this feature, possible like --max-folder-depth=1 (how many levels of folders can be created)

3. Add possibility to run locust inside folder.

Does it make sense to keep this suffix?
If no, remove it please

PyUp.io lets you know when package dependencies are out of date or have security vulnerabilities. It automatically makes a pull request to update the package on GitHub.
On https://pyup.io/ register through GitHub, and connect your organization.

The bot created this issue to inform you that pyup.io has been set up on this repo.
Once you have closed it, the bot will open pull requests for updates as soon as they are available.

Users want to manage files, extend them. It would be great to add such an option as param.

MIT or Apache 2.0?

https://github.com/marketplace/actions/coveralls-github-action