swagger-api / swagger-api/swagger-codegen
Upgrade API client integration tests to use Fake Petstore spec
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
petstore-with-fake-endpoints-models-for-testing.yaml covers a lot more edge cases when comparing with the original one (petstore.yaml)
We'll need to to update petstore.yaml with petstore-with-fake-endpoints-models-for-testing.yaml so to ensure the edge cases are covered moving forward.
API clients using petstore-with-fake-endpoints-models-for-testing.yaml:
- Android
- Bash
- C++ (qt5, cpprest, tizen)
- C#
- Clojure
- Dart
- Elixir
- Flash
- Go
- Groovy
- JavaScript
- Java
- ObjC
- Perl
- PHP
- Python
- Ruby
- Swift (2.x ◻️, 3,x ✅)
- Scala
If anyone wants to work on the enhancement, please reply to let us know. Thank you!
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
Compare modules/swagger-codegen/src/test/resources/2_0/petstore.yaml with petstore-with-fake-endpoints-models-for-testing.yaml first. Then inspect the API client integration tests for the unchecked C++, Dart, Flash, Groovy, Swift, and Scala clients and verify they use the expanded spec when complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi, yaml
- Domain
- api, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100