Testing input fields. Details
Hello everyone! My name is Ivan, third year in testing. At the moment I am working on a mobile fintech project. Today I will show a lazy checklist for testing masks and input fields. Keep the hackneyed phone number for yourself, and we are testing account details!
We will not use the intersection table taught in Yandex Practicum, it is very useful, but due to lack of time, you often have to sketch out a checklist. Maybe you stop filling out the table of boundary values and equivalence classes due to experience? Let's check now)
We have three fields on one page: “Account number”, “BIC”, “Bank name”.
field “Account number”
When you click on a field, a TOUCHBAR (numbers) appears
When you click on the field, the placeholder disappears
The placeholder contains “Enter account number”
Hint “Must start with 4XX” if first digit is not 4
Hint “Must contain 20 digits” after removing focus from field (less than 20 digits)
The hint is not displayed if there is no data in the field (focus is removed from the field)
“Must start with 4XX” prompt when entering incorrectly again
Hints are displayed when you continue typing in another field
Every 4 digits are separated by spaces automatically
Input limit in the field is 20 digits
When entering 20 digits, there is no way to shift the data with additional input (at the beginning, in the middle)
If you copy 40 digits, only the first 20 will be pasted.
Limitation on inserting letters (Cyrillic, Latin, etc.)
Limit on inserting characters
Limitation on inserting emoji
If you copy “Pro1ver2ka3” – only “123” will be pasted
Cut data from a field and paste it back (another field)
When you tap on the field, the cross disappears.
When you remove focus, a cross appears (if there is data in the field)
Clicking on the cross erases the data in the field
The cursor remains at the first character after deletion.
The cursor remains at the end after inserting 20 digits
If the field is covered by the touchbar, the field is scrolled to the visible area
field “BIC”
When you click on a field, a TOUCHBAR (numbers) appears
When you click on the field, the placeholder disappears
The placeholder contains “Enter BIC”
Hint “Must contain 9 digits” after removing focus from field (less than 9 digits)
The hint is not displayed if there is no data in the field (focus is removed from the field)
Hints are displayed when you continue typing in another field
Input limit in the field is 9 digits
When entering 9 digits, there is no way to shift the data with additional dialing
If you copy 40 digits, only the first 9 will be pasted.
Limitation on inserting letters (Cyrillic, Latin, etc.)
Limit on inserting characters
Limitation on inserting emoji
If you copy “Pro1ver2ka3” – only “123” will be pasted
Cut data from a field and paste it back (another field)
When you tap on the field, the cross disappears.
When you remove focus, a cross appears (if there is data in the field)
Clicking on the cross erases the data in the field
The cursor remains at the first character after deletion.
The cursor remains at the end after inserting 9 digits
If the field is covered by the touchbar, the field is scrolled to the visible area
field “Bank name”
When you click on a field, a KEYBOARD appears (letters, numbers, symbols)
Under the field there is a hint “The name will be filled in if the account BIC is found”
When you click on the field, the placeholder disappears
The placeholder contains “Enter the bank name”
Input limit in the field is 50 characters
Input of data in caps is allowed
Check input – Latin/Cyrillic, punctuation marks and mathematical symbols
Limitation on inserting emoji
After entering the BIC, the “Bank name” field is unavailable for input for 1 second.
If the BIC is found, the field is filled in automatically
The “Bank name” field must be filled within 3 seconds after entering the BIC
If the BIC is incorrect or not found, the field can be filled in manually
The field is overwritten when entering another BIC number
The name can be edited/rewritten (Tinkoff to TBank)
Cut data from the field and paste it back
General
When you return to the page, the data is filled in (updating)
When sending a request, there are no extra spaces or data (20, 9 and no more than 50 characters)
In the logs, the data is displayed in accordance with the conditions above.
In the database, data is displayed in accordance with the conditions above.
When the hint is displayed, the field is framed with a color accent
Data is saved when there is no Internet connection or the device is turned off
Elements on the page are rendered identically on all platforms!!!
The Next button is available when all fields on the page are filled in.
The Next button becomes unavailable when data is deleted from one or more fields.
We have specified the main checks, we have a lazy checklist, because it can be improved with a table of boundary values and equivalence classes. I will tell you a secret, the table is rarely used due to lack of time. You have to get by)
The most bugs are in check 22 – elements can differ in height and display – this happens due to the features of the device screen, but there should be no differences in the design of the elements.
This checklist can very well turn out to be 20-30 bugs. This is not a joke, this is the reality of testing fields with a huge set of exceptions. They even came up with a word for this – mask. “Mask on the field” is a set of restrictions when entering data.
For the most attentive:
I intentionally allowed bugs in the layout, check your attentiveness and write in the comments which ORs did not match in your opinion. It would be great to check not only according to the checklist, but also to add your own usability checks.
My contacts QAtoDev
