Page Comparison

n/n	Description	Test case Inputs	Expected result	Step by Step Script	Actual Result
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	person_id is null 2fa_access token instead of access_token
SU2	register 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)	follow the link fill data input sms input password	if found more than one person - return mistake, not update the first one as it is now
SU3	register 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)	follow the link fill data input sms input password	while updating user - person_id is null factor is not updated
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	while updating user - person_id is null factor is not updated
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	update current person
SU6	update user with status is_blocked=true	valid signed content correct OTP valid password	401, User blocked create person	follow the link fill data input sms input password	401, User blocked, create person updated user, linked tax_id
SU7	input incorrect OTP	valid signed content valid password incorrect OTP	403 Error (`Invalid verification code`)	follow the link fill data input sms 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	follow the link fill data input sms input password	422, 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
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

200

422,

created

$addresses.area
SU13	invalid 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	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

Versions Compared

Old Version 6

New Version 7

Key