Test #4123
closed
Story #4687: As a user, I can use either Python or Ruby bindings to interact with Pulp
Test the generated API binds
Description
- Evaluate the best way to test the generated API binds.
One possible solution is to use .json file generated in a certain date, and use to compare with the new one.
- See: generarte-bindings
- Related to Issue #3965: Created Resource schema generated incorrectly added
- Related to Issue #3964: OpenAPI schema requires Progress Report suffix to be 1 char or longer added
- Related to Issue #3850: Return relative URIs (e.g. /pulp/api/v3/repositories/1/) in the API added
- Description updated (diff)
- Priority changed from Normal to High
- Status changed from NEW to ASSIGNED
- Related to Issue #4509: API docs returning different values added
- Status changed from ASSIGNED to MODIFIED
- Related to Task #4104: Add index and headings to REST API docs added
- Status changed from MODIFIED to ASSIGNED
- Assignee changed from kersom to dkliban@redhat.com
- Status changed from ASSIGNED to POST
- Sprint set to Sprint 51
- Status changed from POST to MODIFIED
- Parent issue set to #4687
- Sprint/Milestone set to 3.0.0
- Status changed from MODIFIED to CLOSED - COMPLETE
Also available in: Atom
PDF
.
Add test to compare API bindings
Use the generated OpenAPI schema in json format generated on April/01/2019 as base to compare with generated on the fly API schemas. Main goal is to detect changes in the API schema.
In case of intentional changes, the
stored_open_api.jsonhas to be updated.https://pulp.plan.io/issues/4123 closes #4123