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

openapi-v3-types module: add basic tests #181

Closed
2 of 3 tasks
bajtos opened this issue Apr 20, 2017 · 9 comments
Closed
2 of 3 tasks

openapi-v3-types module: add basic tests #181

bajtos opened this issue Apr 20, 2017 · 9 comments
Assignees
Milestone

Comments

@bajtos
Copy link
Member

bajtos commented Apr 20, 2017

Add basic tests to verify that example OpenAPI v3 documents and Swagger documents (via converter) can be compiled against the type definition. Create test infrastructure that makes it easy to add focused tests in the future.

This is a follow-up issue for #177.

Acceptance Criteria

  • Add validation test for OpenAPI v3 document
  • Add validation test for Swagger document (converted from v3 document)
  • Add scaffolding to allow unit tests in future

BLOCKED BY

@bajtos bajtos changed the title Add basic tests for openapi-spec openapi-spec: add basic tests Apr 20, 2017
@dhmlau dhmlau changed the title openapi-spec: add basic tests openapi-spec v3: add basic tests Sep 6, 2017
@dhmlau dhmlau added the Core-GA label Sep 6, 2017
@bajtos bajtos added the MVP label Nov 3, 2017
@bajtos bajtos changed the title openapi-spec v3: add basic tests openapi-spec module: add basic tests Nov 3, 2017
@kjdelisle kjdelisle changed the title openapi-spec module: add basic tests openapi-v3-spec module: add basic tests Jan 18, 2018
@shimks shimks assigned shimks and unassigned shimks Feb 2, 2018
@jannyHou jannyHou changed the title openapi-v3-spec module: add basic tests openapi-v3-types module: add basic tests Mar 6, 2018
@shimks
Copy link
Contributor

shimks commented Mar 27, 2018

I'm not sure if this issue is valid anymore. We've dropped v3 to v2 conversion from MVP (as far as I know) and we have validation for v3 in @loopback/testlab. We also have some scaffolding in @loopback/openapi-spec-builder.

I think we should repurpose this issue to add in what we discussed here #754 (comment) and then re-estimate it.

@strongloop/lb-next-dev thoughts?

@shimks
Copy link
Contributor

shimks commented Mar 28, 2018

@jannyHou Could you cross off the tasks here that have been done as part of your work on #753?

@jannyHou
Copy link
Contributor

jannyHou commented Mar 28, 2018

@shimks I don't think this is done in #753, we don't have tests for package loopback-next/openapi-v3-types and loopback-next/openapi-spec-builder. I see a bunch of discussion linked to this issue, and am confused by the description

Add basic tests to verify that example OpenAPI v3 documents and Swagger documents (via converter) can be compiled against the type definition

Could you summarize a little bit what are we adding in this issue? tests for openapi-v3-types or openapi-spec-builder or both?

@shimks
Copy link
Contributor

shimks commented Mar 28, 2018

Could you summarize a little bit what are we adding in this issue? tests for openapi-v3-types or openapi-spec-builder or both?

I think the fact that we need to ask this question is an indication that this story needs re-grooming.
@strongloop/lb-next-dev Can we get a discussion going to get the clarification we need for this topic?

@dhmlau
Copy link
Member

dhmlau commented Mar 28, 2018

I guess we need clarification from @bajtos who created this issue?

@dhmlau
Copy link
Member

dhmlau commented Apr 2, 2018

Looking at this issue again, I'm thinking maybe the acceptance criteria is clear enough? The title of this ticket is openapi-v3-types module: add basic tests. Doesn't it mean adding test for at least openapi-v3-types?

Should we leave adding tests for openapi-spec-builder as out-of-scope (thus create new issue to track it) or as part of the acceptance criteria (then we edit the criteria above)?

@shimks
Copy link
Contributor

shimks commented Apr 2, 2018

Now that I've taken a look at this issue again, I think it's fine as it is now :p (sorry for the confusion). I personally think adding in tests for openapi-spec-builder should be done as a part of the task and should have been inferred from the criteria, even if it hasn't been explicitly mentioned

@virkt25 virkt25 added this to the April 2018 milestone Apr 2, 2018
@dhmlau
Copy link
Member

dhmlau commented Apr 2, 2018

ok. i'll remove needs clarification tag then. thanks.

@virkt25 virkt25 self-assigned this Apr 4, 2018
virkt25 added a commit that referenced this issue Apr 10, 2018
virkt25 added a commit that referenced this issue Apr 10, 2018
virkt25 added a commit that referenced this issue Apr 10, 2018
virkt25 added a commit that referenced this issue Apr 11, 2018
virkt25 added a commit that referenced this issue Apr 11, 2018
@virkt25
Copy link
Contributor

virkt25 commented Apr 11, 2018

Add validation test for Swagger document (converted from v3 document) is no longer relevant as the we only support OAS 3 only now.

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

No branches or pull requests

7 participants