Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ISSUE-195 # Generation of Scenarios from OpenAPI specifications (POC) #695

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

javiertuya
Copy link
Collaborator

@javiertuya javiertuya commented Nov 8, 2024

Generation of Scenarios from OpenAPI specifications (POC)

Fixes Issue

PR Branch
https://github.com/javiertuya/zerocode/tree/195-zerocode-openapi-poc

Motivation and Context

This is a proof of concept of a generator of Zerocode scenarios from OpenAPI specifications.

  • Currently implemented in a separate module: zerocode-openapi
  • Provides a single entry point generateAll that takes two arguments:
    • File name or url where the OpenAPI specification is located.
    • A folder where the generated scenarios will be placed (name of scenarios match the name of the path in the specification).
  • Integration tests generate scenarios from the POC demonstrator: Swagger Petstore specification.
  • End to End tests (manual execution) run the generated scenarios agains the real petstore backend.
  • Additional performance test (manual) generates scenarios from the OpenAPI specification of the GitHub REST API.
  • Provisional documentation with more details in the module README.md file

Checklist:

  • New Unit tests were added

    • Covered in existing Unit tests
  • Integration tests were added

    • Covered in existing Integration tests
  • Test names are meaningful

  • Feature manually tested and outcome is successful

  • PR doesn't break any of the earlier features for end users

    • WARNING! This might break one or more earlier earlier features, hence left a comment tagging all reviewrs
  • Branch build passed in CI

  • No 'package.*' in the imports

  • Relevant DOcumentation page added or updated with clear instructions and examples for the end user

    • Not applicable. This was only a code refactor change, no functional or behaviourial changes were introduced
  • Http test added to http-testing module(if applicable) ?

    • Not applicable. The changes did not affect HTTP automation flow
  • Kafka test added to kafka-testing module(if applicable) ?

    • Not applicable. The changes did not affect Kafka automation flow

@authorjapps
Copy link
Owner

Thanks @javiertuya , will have a look. This might take bit of time to fully review it as there are a lot of things for the context.

Also, added @a1shadows @omkar-shitole as the reviewer. Can you guys have a look please?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support OpenAPI Specification
2 participants