ЕСОЗ - публічна документація

Update merge_request tests

n/n
description
inputs
expected result GraphQlactual result GraphQlcomment
UMR1Update merge request without scopes
  • token
missing allowance merge_request:review"extensions": {
"code": "FORBIDDEN",
"exception": {
"missingAllowances": [
"merge_request:write"
]


UMR2Update merge request without role 
  • doctor token
403, FORBIDDEN

401

"error": {
"message": "Invalid access token",
"type": "access_denied"
}


UMR3Update merge request with client not NHS
  • mithril token with correct scopes
  • invalid client id 
403, FORBIDDEN

"code": "FORBIDDEN"

"message": "Current client is not allowed to access this resource",


UMR4Update merge request assigned to other user
  • token
  • invalid id
Current client is not allowed to access this resource

"code": "FORBIDDEN"

"message": "Current client is not allowed to access this resource",

Current user is not allowed to access this resource
UMR5Update merge request which doesn't exist
  • token
  • id doesn't exist
NOT_FOUND

"code": "NOT_FOUND"


UMR6

Update merge request in status

  • TRASH
  • SPLIT
  • MERGE
  • token
  • id
CONFLICT error - 'Incorrect transition status'

 "code": "CONFLICT"

"message": "Incorrect transition status",


UMR7Update merge request in status NEW and next status NEW
  • token
  • id
  • status=NEW
CONFLICT error - 'Incorrect transition status'

 "code": "CONFLICT"

"message": "Incorrect transition status",


UMR8Update merge request in status POSTPONE and next status NEW
  • token
  • id
  • status=NEW
CONFLICT error - 'Incorrect transition status'

 "code": "CONFLICT"

"message": "Incorrect transition status",


UMR9Update merge request in status POSTPONE and next status POSTPONE
  • token
  • id
  • status=POSTPONE
CONFLICT error - 'Incorrect transition status'

 "code": "CONFLICT"

"message": "Incorrect transition status",


UMR10Update MR in status NEW / POSTPONE
  • token
  • id
  • status

Merge Request is updated

  • updated a record by ID
  • there is a record in audit_log with next status
ок
UMR11Update MR in status NEW / POSTPONE as a final decision MERGE
  • token
  • id
  • status

Merge Request is updated

  • updated a record by ID
  • there is a record in audit_log with next status
  • manual_merge_candidates.status=PROCESSED
  • manual_merge_candidates.status.=$status
  • declaration is terminated
  • person is deactivated
ок
UMR12

Update MR in status NEW / POSTPONE as a final decision MERGE and with $person_id=person_id for other requests

  • token
  • id
  • status

Merge Request is updated

  1. updated a record by ID
  2. there is a record in audit_log with next status
  3. manual_merge_candidates.status=PROCESSED

  4. manual_merge_candidates.status.=$status

  5. declaration is terminated

  6. person is deactivated


  7. found all record with $person_id=person_id and status=NEW
    1. changed status=PROCESSED
    2. decision=MERGE
    3. status_reason = auto_merge
    4. declarations are terminated
    5. persons are deactivated




UMR13

Update MR in status NEW / POSTPONE as a final decision MERGE and with $person_id=master_person_id other requests

  • token
  • id
  • status

Merge Request is updated

  1. updated a record by ID
  2. there is a record in audit_log with next status
  3. manual_merge_candidates.status=PROCESSED

  4. manual_merge_candidates.status.=$status

  5. declaration is terminated

  6. person is deactivated

  7. found all record with $person_id=master_person_id and status=NEW
    1. changed status=PROCESSED
    2. decision=MERGE
    3. status_reason = auto_merge
    4. for such pairs found person_id and their
      1. declarationі are terminated
      2. persons are deactivated


UMR14Update MR in status NEW / POSTPONE as a final decision SPLIT
  • token
  • id
  • status

Merge Request is updated

  • updated a record by ID
  • there is a record in audit_log with next status
  • manual_merge_candidates.status=PROCESSED
  • manual_merge_candidates.status.=$status


ЕСОЗ - публічна документація