Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


n/nDescriptionTest case InputsExpected resultStep by Step ScriptActual Result
SU1register 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)
  1. follow the link
  2. fill data
  3. input sms
  4. input password
  • person_id is null
  • 2fa_access token instead of access_token
SU2register new user for existing 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)
  1. follow the link
  2. fill data
  3. input sms
  4. input password
  • if found more than one person - return mistake, not update the first one as it is now
SU3register new person for mithril.user 
  • valid signed content
  • correct OTP
  • valid password

200, 

create

  • person (change updated_at)
  • user_role 
  • authentification_factor
  • token (access_token)

update

  • user (tax_id, mpi)
  1. follow the link
  2. fill data
  3. input sms
  4. input password
  • while updating user -  person_id is null
  • factor is not updated
SU4link 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)
  1. follow the link
  2. fill data
  3. input sms
  4. input password
  • while updating user -  person_id is null
  • factor is not updated
SU5existing matching person with status='INACTIVE'
  • valid signed content
  • correct OTP
  • valid password
create new mpi.person_id
  1. follow the link
  2. fill data
  3. input sms
  4. input password
update current person
SU6update user with status is_blocked=true
  • valid signed content
  • correct OTP
  • valid password
401, User blocked
create person

  1. follow the link
  2. fill data
  3. input sms
  4. input password

401, User blocked,

create person

updated user, linked tax_id

SU7input incorrect OTP 
  • valid signed content
  • valid password
  • incorrect OTP
403 Error (`Invalid verification code`)
  1. follow the link
  2. fill data
  3. input sms
  4. input password

for existing user - 200, created

for new user - 422, $otp

SU8

input password doesn't meet Password policy requirements 

  • valid signed content
  • invalid password
  • correct OTP
Password Policy
  1. follow the link
  2. fill data
  3. input sms
  4. input password
422, Password does not meet complexity requirements
SU9input email doesn't match jwt token
  • invalid email
  • valid password
  • correct OTP
409 Error (`Email in signed content is incorrect`)
  1. follow the link
  2. fill data
  3. input sms
  4. input password
409, Email in signed content is incorrect
SU10input 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`)
  1. follow the link
  2. fill data
  3. input sms
  4. input password

409, Input last_name doesn't match name from DS

Input first_name doesn't match name from DS

SU11tax_id in payload<> DS.tax_id
  • invalid tax_id
  • valid password
  • correct OTP
409 ('Invalid tax_id')
  1. follow the link
  2. fill data
  3. input sms
  4. input password
409, Registration person and person that sign should be the same
SU12input area & settlement_id settlement_name & doesn't match uaadresses
  • invalid area, settlement_id & settlement_name
422 
  1. follow the link
  2. fill data
  3. input sms
  4. input password
200, created
SU13invalid dictionary fields
  • invalid :
    • documents.type
    • gender
    • address.type-RESIDENCE&RESIDENCE
    • authentication_methods.type='OFFLINE'
    • phones.type and emergency_contact.phones.type
    • addresses.settlement_type
    • addresses.street_type
422 $field
  1. follow the link
  2. fill data
  3. input sms
  4. input password

SU14phone in authentication_methods doesn't match the phone with invalid authentication_methods.phone422, 'incorrect authentication phone number'
  1. follow the link
  2. fill data
  3. input sms
  4. input password
422, invalid code, $otp