swagger-api / swagger-api/swagger-codegen

Generate test clients for stress testing

Open
#1,910 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Client: JMeter Enhancement: Feature
Dominant language
Mustache
Stars
17.8k
Forks
6k
PR merge metrics
No merged PRs in 30d

Description

Client code currently generated by swagger-codegen is meant for manual invocation.

It would be a revolution in agility if, instead of waiting for test code to be written manually, that immediately after a change in swagger specs, for performance benchmarks be obtained based on generated client test code and test runs.

Provide an example tutorial of how to use swagger-codegen to automatically create and run performance tests. Perhaps use testing frameworks such as JMeter, Gatlin, LoadRunner, etc.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named. Start by reviewing how swagger-codegen generates client code, then compare the proposed JMeter, Gatling, and LoadRunner approaches. Done would be a tutorial showing how a Swagger specification change leads to generated performance-test code and test runs.

Written by the indexing model from the issue text.

Assessment

Tech stack
openapi
Domain
performance, testing-qa, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.