swagger-api/swagger-codegen

Upgrade API server integration tests to use Fake Petstore spec #5419

Open

#5,420 opened on 2017年4月19日

GitHub で見る
 (8 comments) (0 reactions) (0 assignees)HTML (12,701 stars) (5,474 forks)batch import
Feature List: API serversServer: C-SharpServer: ErlangServer: GoServer: HaskellServer: JavaServer: NodejsServer: PHPServer: PerlServer: PythonServer: RubyServer: ScalaServer: Springhelp wanted

説明

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 servers using petstore-with-fake-endpoints-models-for-testing.yaml:

  • C# (NancyFx, ASP.net Core)
  • Elixir
  • Erlang
  • Go
  • Haskell Servant
  • JavaScript/NodeJS
  • Java (MSF4J, Spring, Undertow, JAX-RS: CDI, CXF, Inflector, RestEasy)
  • PHP (Lumen, Slim, Silex, Zend Expressive)
  • Python Flask
  • Ruby (Sinatra, Rails)
  • Scala Finch
  • Scala Scalatra

If anyone wants to work on the enhancement, please reply to let us know. Thank you!

コントリビューターガイド

技術スタック
csharpelixirgonodejsjavaphppythonrubyscala
領域
backendtesting
Issue 種別
test
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
3-5 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Familiarity with Swagger/OpenAPI specKnowledge of a specific language and test framework
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
50
調査方針
The issue asks to replace the original petstore.yaml with petstore with fake endpoints models for testing.yaml in the integration tests for multiple API server implementations. The fake endpoints spec covers more edge cases. To start, review the differences between the two YAML files and choose one language from the checkboxes. Update the test files for that language (e.g., the corresponding test resource files) to use the new spec and run the tests to verify. The pull requests mentioned in comments may provide guidance on expected changes. Maintainers discussed planning but no recent activity; check the repo for any ongoing work.