1.

Flow when user enters a number not found in contacts but a valid phone number, the app
showed the contact with display of phone number +6001XXXXXXXX. FAIL
[@Shamini it is not an issue as the entered number is not a active wallet number].

2. Flow when user enters a number not found in contacts but a valid phone number,
subsequently when the same phone number entered, the app showed the contact with
display of phone number with additional
[@Shamini this is expected as we are always prepending country code to the entered
number, @Sam can you please confirm].

3. Then subsequently when user tried to enter another new valid number, app is not returning
the valid number to user. FAIL.
[@Shamini this fixed and will let you know once it is available for testing].

4. Flow when user enters a number not found in contacts but an invalid phone number & also
user when user enters full phone number which is invalid should also throw an error message
FAIL
[@Shamini the above fix will solve the part of this issue and it will not through invalid
error message for all the invalid phone numbers. The rule behind the message to appear
is if the entered numbers length is less than 3].

5. Validation Error message shown phone number is invalid still remains even when user has
removed the invalid phone number. FAIL
[@Shamini this is fixed and will let you know once it is available for testing].

6. When selecting a contact, if the phone number is Wallet active: FAIL. Comparing with Figma
the ewallet number format is +601XXXXXXXX.
[@Shamini this is fixed and will let you know once it is available for testing].

7. When selecting a contact, if the phone number is Wallet inactive: FAIL. Comparing with Figma
the ewallet number format is +601XXXXXXXX.
[@Shamini it is same as the above issue. One fix will resolve both the issues].

8. When selecting a contact, Not found in contacts and is Wallet active: FAIL. Comparing with
Figma the user icon used is incorrect, it should be the user icon.
[@Shamini this is fixed and will let you know once it is available for testing].

9. When selecting a contact, Not found in contacts and is Wallet inactive: FAIL. Comparing with
Figma the format of phone number shown is incorrect +6001XXXXXXXX.
[@Shamini it is not an issue].
10. No Issue
11. If the app was left in idle(background for a few days with contacts allowed in device) and then
user accesses the app once again. Shouldn’t the app directly redirect the user to Select
Contacts page? FAIL
[Will check with Ahmed]

12. App has NO access to phone contacts and user enters a valid number with format +6018 but
app throws invalid number message and then when user continues to enter the valid number
app does not return either a validation message or a number to user. Incorrect Behavior FAIL
[@Shamini this is similar to issue 4 ].
13. App has NO access to phone contacts and user enters invalid number format +60XXXXXXXXX
but it is 9 digit, app displayed a phone number and when user entered 10 digit number there
was no validation message being returned and subsequently when user entered a valid
number which exist in recent contact it did not display the contact as well. FAIL
[@Shamini this is similar to issue 4 and for the point 10 digit number validation we don’t have
any max limitation on the number user is trying to enter].