swagger-api/swagger-codegen

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

Open

#5,420 创建于 2017年4月19日

在 GitHub 查看
 (8 评论) (0 反应) (0 负责人)HTML (12,701 star) (5,474 fork)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
议题类型
test
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
3-5 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
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.