| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Bumps [org.junit.jupiter:junit-jupiter](https://github.com/junit-team/junit-framework) from 5.13.1 to 5.13.2. - [Release notes](https://github.com/junit-team/junit-framework/releases) - [Commits](junit-team/junit-framework@r5.13.1...r5.13.2) --- updated-dependencies: - dependency-name: org.junit.jupiter:junit-jupiter dependency-version: 5.13.2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Test Results 318 files - 632 318 suites - 632 2m 50s ⏱️ - 5m 32s Results for commit 31a80ca. ± Comparison against base commit 64f3a9d. This pull request removes 462 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@4f9bda4> graphql.ScalarsBooleanTest ‑ serialize throws exception for invalid input <java.lang.Object@4386ddd4> graphql.ScalarsIDTest ‑ parseValue allows any object via String.valueOf <java.lang.Object@2d2686f8> graphql.ScalarsIDTest ‑ serialize allows any object via String.valueOf <java.lang.Object@232b64f2> graphql.ScalarsIntTest ‑ parseValue throws exception for invalid input <java.lang.Object@776bc40d> graphql.ScalarsIntTest ‑ serialize throws exception for invalid input <java.lang.Object@3960e798> graphql.execution.instrumentation.TracingInstrumentationTest ‑ do not trace introspection information [testExecutionStrategy: <graphql.execution.AsyncExecutionStrategy@1e194b5f fieldCollector=graphql.execution.FieldCollector@731eb971 executionStepInfoFactory=graphql.execution.ExecutionStepInfoFactory@25314d29 dataFetcherExceptionHandler=graphql.execution.SimpleDataFetcherExceptionHandler@15338d3c resolvedType=graphql.execution.ResolveType@41246f76>, #0] graphql.execution.instrumentation.TracingInstrumentationTest ‑ do not trace introspection information [testExecutionStrategy: <graphql.execution.AsyncSerialExecutionStrategy@6800d6c0 fieldCollector=graphql.execution.FieldCollector@6153ec91 executionStepInfoFactory=graphql.execution.ExecutionStepInfoFactory@3ee6012 dataFetcherExceptionHandler=graphql.execution.SimpleDataFetcherExceptionHandler@78fa1c7e resolvedType=graphql.execution.ResolveType@16226377>, #1] graphql.execution.instrumentation.TracingInstrumentationTest ‑ tracing captures timings as expected [testExecutionStrategy: <graphql.execution.AsyncExecutionStrategy@38d4d184 fieldCollector=graphql.execution.FieldCollector@b5d8f6f executionStepInfoFactory=graphql.execution.ExecutionStepInfoFactory@58b1a587 dataFetcherExceptionHandler=graphql.execution.SimpleDataFetcherExceptionHandler@760215d3 resolvedType=graphql.execution.ResolveType@6844a266>, #0] graphql.execution.instrumentation.TracingInstrumentationTest ‑ tracing captures timings as expected [testExecutionStrategy: <graphql.execution.AsyncSerialExecutionStrategy@70ac7e00 fieldCollector=graphql.execution.FieldCollector@79cec730 executionStepInfoFactory=graphql.execution.ExecutionStepInfoFactory@17db566 dataFetcherExceptionHandler=graphql.execution.SimpleDataFetcherExceptionHandler@2ad44ed9 resolvedType=graphql.execution.ResolveType@391b79fd>, #1] … graphql.schema.fetching.LambdaFetchingSupportTest ‑ different class loaders induce certain behaviours |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Bumps org.junit.jupiter:junit-jupiter from 5.13.1 to 5.13.2.
Release notesSourced from org.junit.jupiter:junit-jupiter's releases.
CommitsDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: