Avoid rare TCK test failure by andimarek · Pull Request #3975 · graphql-java/graphql-java
Test Results
315 files ±0 315 suites ±0 2m 27s ⏱️ +2s
3 647 tests ±0 3 642 ✅ ±0 5 💤 ±0 0 ❌ ±0
3 736 runs ±0 3 731 ✅ ±0 5 💤 ±0 0 ❌ ±0
Results for commit dcb9b05. ± Comparison against base commit c16cf96.
This pull request removes 150 and adds 128 tests. Note that renamed tests count towards both.
?
__schema { types { fields { args { type { name fields { name }}}}}}
__schema { types { fields { type { name fields { name }}}}}
__schema { types { inputFields { type { inputFields { name }}}}}
__schema { types { interfaces { fields { type { interfaces { name } } } } } }
__schema { types { name} }
__type(name : "t") { name }
a1: __schema { types { name} }
a1: __type(name : "t") { name }
a2 : __type(name : "t1") { name }
…
graphql.ScalarsBooleanTest ‑ parseValue throws exception for invalid input <java.lang.Object@525eac20>
graphql.ScalarsBooleanTest ‑ serialize throws exception for invalid input <java.lang.Object@51e722fc>
graphql.ScalarsIDTest ‑ parseValue allows any object via String.valueOf <java.lang.Object@79e72fac>
graphql.ScalarsIDTest ‑ serialize allows any object via String.valueOf <java.lang.Object@24c67fda>
graphql.ScalarsIntTest ‑ parseValue throws exception for invalid input <java.lang.Object@51476b96>
graphql.ScalarsIntTest ‑ serialize throws exception for invalid input <java.lang.Object@60d22fce>
graphql.execution.instrumentation.TracingInstrumentationTest ‑ do not trace introspection information [testExecutionStrategy: <graphql.execution.AsyncExecutionStrategy@d763063 fieldCollector=graphql.execution.FieldCollector@4debf7c4 executionStepInfoFactory=graphql.execution.ExecutionStepInfoFactory@34b3fc15 dataFetcherExceptionHandler=graphql.execution.SimpleDataFetcherExceptionHandler@75096f5c resolvedType=graphql.execution.ResolveType@49c0bcb6>, #0]
graphql.execution.instrumentation.TracingInstrumentationTest ‑ do not trace introspection information [testExecutionStrategy: <graphql.execution.AsyncSerialExecutionStrategy@707f2bbc fieldCollector=graphql.execution.FieldCollector@4e32c960 executionStepInfoFactory=graphql.execution.ExecutionStepInfoFactory@25bf91c dataFetcherExceptionHandler=graphql.execution.SimpleDataFetcherExceptionHandler@60028d15 resolvedType=graphql.execution.ResolveType@69296862>, #1]
graphql.execution.instrumentation.TracingInstrumentationTest ‑ tracing captures timings as expected [testExecutionStrategy: <graphql.execution.AsyncExecutionStrategy@406570d2 fieldCollector=graphql.execution.FieldCollector@6e58b55 executionStepInfoFactory=graphql.execution.ExecutionStepInfoFactory@60881be8 dataFetcherExceptionHandler=graphql.execution.SimpleDataFetcherExceptionHandler@31b78ac5 resolvedType=graphql.execution.ResolveType@5a3f9fc1>, #0]
graphql.execution.instrumentation.TracingInstrumentationTest ‑ tracing captures timings as expected [testExecutionStrategy: <graphql.execution.AsyncSerialExecutionStrategy@61cd05ab fieldCollector=graphql.execution.FieldCollector@233d6218 executionStepInfoFactory=graphql.execution.ExecutionStepInfoFactory@2c560bf1 dataFetcherExceptionHandler=graphql.execution.SimpleDataFetcherExceptionHandler@2192ffe8 resolvedType=graphql.execution.ResolveType@287b562c>, #1]
…