How to create SDK for testing
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 177
- Forks
- 87
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Please use this template for tools that cannot be tagged on GitHub. If your tool is on GitHub use the
openapi3andopenapi31tags to allow your data to be collected automatically.
Tool Properties
Please replace all placeholders marked in bold in the bullets below with the requested information. Use plain text for your information.
- Display name: Enter the display name for the tool in the repository
- Description: Provide a description of your tool. This will provide users with valuable information about your tool and be used to as a means to classify your tool correctly.
- Repository: If you tool is open source but not on GitHub please provide a link to your repository.
- Homepage: Provide a link to your homepage. If you have provided a repository you can leave this blank if you wish.
OpenAPI Versions
Please indicate the versions of OpenAPI supported by your tool by marking them true or false below.
- 3.1: false
- 3.0: false
- 2.0: false
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file, test, or entry point is mentioned. Start by clarifying whether this is a tool-submission request or an SDK-testing question; completion would require a specific tool description, repository or homepage, and declared OpenAPI versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100