Issues/216 - Import e2e cucumber tests into casper-java-sdk #184
meywoodAnnotations
3 errors, 7 warnings, and 1 notice
|
Generate "Secp256k1" Account Failed.:
file:cspr-standard-tests-resources/features/deploys_generated_keys.feature#L13
Scenario: Generate "Secp256k1" Account
Step: that a "Secp256k1" sender key is generated
Error:
java.lang.AssertionError:
Expected: is not null
but: was null
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:6)
at com.casper.sdk.e2e.steps.DeployGeneratedKeys.thatSenderKeyIsGenerated(DeployGeneratedKeys.java:80)
at ✽.that a "Secp256k1" sender key is generated(file:///home/runner/work/casper-java-sdk/casper-java-sdk/cspr-standard-tests-resources/features/deploys_generated_keys.feature:13)
|
|
query_global_state by block hash Failed.:
file:cspr-standard-tests-resources/features/query_global_state.feature#L4
Scenario: query_global_state by block hash
Step: that a valid block hash is known
Error:
java.lang.AssertionError:
Expected: is <true>
but: was <false>
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:6)
at com.casper.sdk.e2e.steps.QueryGlobalStateStepDefinitions.waitForBlockAdded(QueryGlobalStateStepDefinitions.java:262)
at com.casper.sdk.e2e.steps.QueryGlobalStateStepDefinitions.thatAValidBlockHashIsKnown(QueryGlobalStateStepDefinitions.java:75)
at ✽.that a valid block hash is known(file:///home/runner/work/casper-java-sdk/casper-java-sdk/cspr-standard-tests-resources/features/query_global_state.feature:4)
|
|
build
Process completed with exit code 1.
|
|
build
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v2, JamesIves/[email protected], deblockt/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Cucumber report summary:
test#L0
21 Scenarios (2 failed, 2 undefined, 17 passed)
188 Steps (2 failed, 2 undefined, 14 skipped, 170 passed)
|