Skip to content
CI/CD GreenCityUser

Response status is 200 instead 400 when an invalid parameter was entered in the placestatus #1280

Sign in to view logs

Response status is 200 instead 400 when an invalid parameter was entered in the placestatus

Response status is 200 instead 400 when an invalid parameter was entered in the placestatus #1280

Re-run triggered September 9, 2024 11:02
@holotsvanholotsvan
#393
response-status-is-200-instead-400-when-an-invalid-parameter-was-entered-in-the-placestatus
Status Failure
Total duration 1m 30s
Artifacts –

main.yml

on: pull_request
build
1m 18s
build
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 7 warnings
greencity.security.controller.OwnSecurityControllerTest ► setPassword: core/target/surefire-reports/TEST-greencity.security.controller.OwnSecurityControllerTest.xml#L0
Failed test found in: core/target/surefire-reports/TEST-greencity.security.controller.OwnSecurityControllerTest.xml Error: org.mockito.exceptions.verification.opentest4j.ArgumentsAreDifferent:
greencity.security.controller.OwnSecurityControllerTest ► updatePasswordTest: core/target/surefire-reports/TEST-greencity.security.controller.OwnSecurityControllerTest.xml#L0
Failed test found in: core/target/surefire-reports/TEST-greencity.security.controller.OwnSecurityControllerTest.xml Error: org.mockito.exceptions.verification.opentest4j.ArgumentsAreDifferent:
greencity.security.controller.OwnSecurityControllerTest ► hasPassword: core/target/surefire-reports/TEST-greencity.security.controller.OwnSecurityControllerTest.xml#L0
Failed test found in: core/target/surefire-reports/TEST-greencity.security.controller.OwnSecurityControllerTest.xml Error: org.mockito.exceptions.verification.opentest4j.ArgumentsAreDifferent:
greencity.security.controller.OwnSecurityControllerTest ► deleteUser: core/target/surefire-reports/TEST-greencity.security.controller.OwnSecurityControllerTest.xml#L0
Failed test found in: core/target/surefire-reports/TEST-greencity.security.controller.OwnSecurityControllerTest.xml Error: org.mockito.exceptions.verification.opentest4j.ArgumentsAreDifferent:
build
Failed test were found and 'fail-on-error' option is set to true
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@v1, dorny/test-reporter@v1.5.0. 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 following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-java@v1, dorny/test-reporter@v1.5.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-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/