-
Notifications
You must be signed in to change notification settings - Fork 146
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
test(parser): refactor appsync schema tests #3388
test(parser): refactor appsync schema tests #3388
Conversation
7d53e05
to
2d84ccd
Compare
2d84ccd
to
821a5d4
Compare
Hi @svozza, we'll try to review this by early next week - thank you for your patience! |
821a5d4
to
f3a6ad4
Compare
No worries, I know Re:Invent has taken up most of the team's capacity. |
f3a6ad4
to
5d49edb
Compare
5d49edb
to
0a4b414
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your patience and for the PR.
I have left a couple request for changes but I am a big fan of the overall direction of the PR. Appreciate it!
0a4b414
to
7925b3d
Compare
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the PR and for the patience!
@aws-powertools/lambda-typescript No related issues found. Please ensure 'pending-release' label is applied before releasing. |
Summary
As mentioned in #3305, rather than have lots of JSON events that we have to read from the filesystem, we should have one event that we extend/amend to suit each test case. This PR refactors the AppSync schema tests to do this.
Changes
omit
function topackages/parser/tests/unit/schema/utils.ts
that allow us to give a list of fields to be omitted from an object. This is useful for testing.invalid schemas so we can can test where properties that must be present are not.Issue number:
n/a
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.