Description
I would like to create a Challenge for the microprofile-graphql tck.
Please see below:
The relevant specification version and section number(s)
https://github.com/eclipse/microprofile-graphql/tree/master/server/tck - 2.0
The coordinates of the challenged test(s)
org.eclipse.microprofile.graphql:microprofile-graphql-tck:2.0
The following tests in the errorHandling tests - https://github.com/eclipse/microprofile-graphql/tree/master/server/tck/src/main/resources/tests/errorHandling
- createNewNullNamedHero
- createNewUnnamedHero
- invalidDataTypeValue
- invalidEnumValue
- unknownField
- unknownMutation
- unknownQuery
The exact TCK version
org.eclipse.microprofile.graphql:microprofile-graphql-tck:2.0
The implementation being tested, including name and company
- Helidon MP - https://github.com/helidon-io/helidon/
- Oracle Corporation
A full description of why the test is invalid and what the correct behavior is believed to be
I'm upgrading our helidon graphql impl to graphql-java latest, 20.3, and seeing the tck error handling is failing on the errorHandling tests because the error messages that the TCK is expecting have changed.
As an example in unknownMutation.log, previously the tck expected
"message": "Validation error of type FieldUndefined: Field 'createNewHeroCat' in type 'Mutation' is undefined @ 'createNewHeroCat'",`
But with latest graphql-java (20.3) i see
"message": "Validation error (FieldUndefined@[createNewHeroCat]) : Field 'createNewHeroCat' in type 'Mutation' is undefined"
Same message meaning but slightly different output.
Any supporting material; debug logs, test output, test logs, run scripts, etc.
createNewNullNamedHero.log
createNewUnnamedHero.log
invalidDataTypeValue.log
invalidEnumValue.log
unknownField.log
unknownMutation.log
unknownQuery.log