| n/n | Description | Test case Inputs | Expected result | Step by Step Script | Actual Result | Actual Result FE |
|---|
| SU1 | register new person and new user | - valid signed content
- correct OTP
- valid password
| 200, create - person
- user (tax_id, mpi)
- user_role
- authentification_factor
- token (access_token)
| - follow the link
- fill data
- input sms
- input password
| 200, create - person
- user (tax_id, mpi)
- user_role
- authentification_factor
- token (access_token)
| not correct redirect |
| SU2 | register new user for existing unique mpi.person | - valid signed content
- correct OTP
- valid password
| 200, update - person (change updated_at)
create - user (tax_id, mpi)
- user_role
- authentification_factor
- token (access_token)
| - follow the link
- fill data
- input sms
- input password
| 200, update - person (change updated_at)
create - user (tax_id, mpi)
- user_role
- authentification_factor
- token (access_token)
| 200, user is updated |
| SU2.1 | register new user for duplicated mpi.person | - valid signed content
- correct OTP
- valid password
| Error 409, "Person is duplicated" | - follow the link
- fill data
- input sms
- input password
| Error 409, Person duplicated | no error |
| SU3 | register new person for mithril.user | - valid signed content
- correct OTP
- valid password
| 200, create - person (change updated_at)
- user_role
- token (access_token)
update - user (tax_id, mpi)
- authentification_factor
| - follow the link
- fill data
- input sms
- input password
| 200, create - person (change updated_at)
- user_role
- token (access_token)
update - user (tax_id, mpi)
- authentification_factor
| 200 |
| SU4 | link existing person and existing mithril.user | - valid signed content
- correct OTP
- valid password
| 200, update - user (tax_id, mpi)
- person (change updated_at)
create - user_role
- authentification_factor
- token (access_token)
| - follow the link
- fill data
- input sms
- input password
| 200, update - user (tax_id, mpi)
- person (change updated_at)
create - user_role
- authentification_factor
- token (access_token)
| 200 |
| SU5 | existing matching person with status='INACTIVE' | - valid signed content
- correct OTP
- valid password
| create new mpi.person_id | - follow the link
- fill data
- input sms
- input password
| create new mpi.person_id | new person created |
| SU6 | update user with status is_blocked=true | - valid signed content
- correct OTP
- valid password
| 401, User blocked
| - follow the link
- fill data
- input sms
- input password
| 401, User blocked | КОРИСТУВАЧА ЗАБЛОКОВАНО |
| SU7 | input incorrect OTP | - valid signed content
- valid password
- incorrect OTP
| 422 Error $otp | - follow the link
- fill data
- input sms
- input password
| 422, $otp | 422 person is created |
| SU8 | input password doesn't meet Password policy requirements | - valid signed content
- invalid password
- correct OTP
| Password Policy | - follow the link
- fill data
- input sms
- input password
| 422, Password does not meet complexity requirements | Password does not meet complexity requirements |
| SU9 | input email doesn't match jwt token | - invalid email
- valid password
- correct OTP
| 409 Error (`Email in signed content is incorrect`) | - follow the link
- fill data
- input sms
- input password
| 409, Email in signed content is incorrect | -- |
| SU10 | input name doesn't match name from DS | - invalid first_name and last_name
- valid password
- correct OTP
| 422 Error (`Input name doesn't match name from DS`) | - follow the link
- fill data
- input sms
- input password
| 409, Input last_name doesn't match name from DS Input first_name doesn't match name from DS | first_name doesn't match name from DS |
| SU11 | tax_id in payload<> DS.tax_id | - invalid tax_id
- valid password
- correct OTP
| 409 ('Invalid tax_id') | - follow the link
- fill data
- input sms
- input password
| 409, Registration person and person that sign should be the same | -- |
| SU12 | input area & settlement_id settlement_name & doesn't match uaadresses | - invalid area, settlement_id & settlement_name
| 422 | - follow the link
- fill data
- input sms
- input password
| 422, $addresses.area | -- |
| SU13 | invalid dictionary fields | - invalid :
- documents.type
- gender
- address.type-RESIDENCE&RESIDENCE
- address.type-RESIDENCE
- authentication_methods.type='OFFLINE'
- phones.type and emergency_contact.phones.type
- addresses.settlement_type
- addresses.street_type
| 422 $field | - follow the link
- fill data
- input sms
- input password
|
| -- |
| SU14 | phone in authentication_methods doesn't match the phone with | invalid authentication_methods.phone | 422, 'incorrect authentication phone number' | - follow the link
- fill data
- input sms
- input password
| 422, invalid code, $otp |
|