Skip to content
GitLab

[k6] OpenAPI code generator for k6 API load-testing tool (ES5.1+)

Merged Administrator requested to merge github/fork/k6io/feature/k6 into master

Created by: mostafa

k6 is an API load-testing tool created by Load Impact AB to help developers and DevOps people test the performance of their APIs. It is written in Go, and is scriptable in JavaScript, supporting ES5.1+. At Load Impact, we have converters/codegens for HAR files, Postman collections and JMeter to help users of k6 easily be onboard to our tool.

Since we focus on API load-testing, we thought it would be a good idea to create a Swagger/OpenAPI code generator, too. So, after much research, we found that this project is the officially developed and maintained one that we can reliably put our efforts on. Thus we created this code generator, to help generate k6 scripts from Swagger 2.0 specification documents.

This is our first PoC and we definitely would like to hear your feedback to improve it further. There are some questions for the official maintainers:

  1. Should we also edit the README.md and add ourselves as Template Creators and Technical Committee for k6?
  2. Does our implementation seem like a good starting point for further improving the project?

We really appreciate your feedback on this. Note: On @wing328's suggestion I have ported the code from https://github.com/swagger-api/swagger-codegen/pull/10013 to this project.

PR checklist

  • Read the contribution guidelines.
  • If contributing template-only or documentation-only changes which will change sample output, build the project before.
  • Run the shell script(s) under ./bin/ (or Windows batch scripts under.\bin\windows) to update Petstore samples related to your fix. This is important, as CI jobs will verify all generator outputs of your HEAD commit, and these must match the expectations made by your contribution. You only need to run ./bin/{LANG}-petstore.sh, ./bin/openapi3/{LANG}-petstore.sh if updating the code or mustache templates for a language ({LANG}) (e.g. php, ruby, python, etc).
  • File the PR against the correct branch: master, 4.3.x, 5.0.x. Default: master.
  • Copy the technical committee to review the pull request if your PR is targeting a particular programming language.