-
Notifications
You must be signed in to change notification settings - Fork 44
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(i): Update mut. tests to make use of mut. system #1853
test(i): Update mut. tests to make use of mut. system #1853
Conversation
6662c9b
to
ad116a2
Compare
Codecov ReportPatch coverage has no change and project coverage change:
@@ Coverage Diff @@
## develop #1853 +/- ##
===========================================
- Coverage 70.37% 70.26% -0.11%
===========================================
Files 232 232
Lines 24180 24192 +12
===========================================
- Hits 17016 16998 -18
- Misses 6003 6029 +26
- Partials 1161 1165 +4
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 7 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
c64d1f5
to
efde22c
Compare
tests/integration/mutation/update/field_kinds/one_to_many/with_alias_test.go
Show resolved
Hide resolved
tests/integration/mutation/update/field_kinds/one_to_many/with_alias_test.go
Show resolved
Hide resolved
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.
The PR looks fine for what it does, however I have a non-blocking question, doesn't the use of mutation system over the actual gql queries like we were doing it before now introduce a gap between integration testing a client's actual end-to-end use case?
Only visually, the mutation queries are still executed by the tests. That loss of visibility is a cost that I am willing to pay for the increased coverage. |
b859dc7
to
423decf
Compare
- TestMutationCreateOneToMany_AliasedRelationNamToLinkFromSingleSide_NoIDFieldError was removed as it is already tested. The first create has no impact on the outcome of the test. - TestMutationCreateOneToMany_RelationIDToLinkFromSingleSide_NoIDFieldError was removed for the same reasons.
These tests now already exist in the mutation directory
These tests now already exist in the mutation directory
This test now already exist in the mutation directory
423decf
to
e7242e1
Compare
…1853) ## Relevant issue(s) Resolves sourcenetwork#1851 ## Description Updates the mutation tests to make use of mutation system. A handful of collection based tests still exist, as they test stuff that does not yet have support in the new mutation test system (filter, UpdateWithKey(s)). These should be moved later when such support is added. Similarly, the new mutation system does not yet support txns, so the gql request based txn tests remain as gql tests for now. sourcenetwork#1703 Was linked up to tests in this PR, and sourcenetwork#1852 and sourcenetwork#1854 were discovered. Fixing them is out of scope here. Update: It does now fix a bug in the http client collection.Create[Many] functions, as it was easier to fix than to open a ticket.
Relevant issue(s)
Resolves #1851
Description
Updates the mutation tests to make use of mutation system.
A handful of collection based tests still exist, as they test stuff that does not yet have support in the new mutation test system (filter, UpdateWithKey(s)). These should be moved later when such support is added.
Similarly, the new mutation system does not yet support txns, so the gql request based txn tests remain as gql tests for now.
#1703 Was linked up to tests in this PR, and #1852 and #1854 were discovered. Fixing them is out of scope here.
Update: It does now fix a bug in the http client collection.Create[Many] functions, as it was easier to fix than to open a ticket.
Recommend reviewing commit by commit, nothing to fancy is going on, but it might make stuff more obvious.