There are many situations to consider when testing any web form. Although the content of each form is different, we list possible errors that may be useful for you to consider. It is up to you to determine the points you will pay attention to according to the content of your form. let’s get started!
- Only uppercase and lowercase letters can be written in the name part of the forms, if numbers or special characters are written, the operation should not be successful.
- Where numeric data such as phone numbers and postal codes are entered, only numbers should be entered.
- The phone number must be in the valid format for the selected country, if it is in an invalid format, the system should not accept it.
- An invalid/incorrect email address should not be able to register or login.
- Passwords to be generated must be case-sensitive.
- If special characters are required to be used in the password, the password attempted to be created should not be accepted unless special characters are created in the password.
- If an attempt is made to create a new registration with a previously registered email address for the current application/product, the system should fail.
- If an attempt is made to create a new record with a previously registered phone number with the current application/product, the system should malfunction.
- The process should not be continued until the required fields are filled.
- The system should fail when attempting to generate too short or too long passwords for passwords outside the defined range of numbers.
- The password must not be visible and must remain hidden.
- If the name-surname will not be accepted as a password, the system will fail if the name-surname is entered into the system.
- If the date of birth cannot be a password, the system should give an error if the registered birth date is entered as a password.
- Consecutive numbers should not be a password, and if consecutive numbers are entered as a password, the system must malfunction.
- If the username is being created, if the username was previously taken by another user, the system should fail.
- If there is a membership agreement or other mandatory agreement, these agreements should not be continued without being accepted.
- If there is an age restriction; If the desired age limit is greater than the birth date entered as registration, the system should fail.
- If there is a membership with linked accounts, attention should be paid to parallel situations such as logging in with a Facebook account linked to the email address entered.
- If verification by e-mail is required while signing up, if the verification code from the e-mail address is entered incorrectly, the system will fail.
- location is in desired conditions; If VPN is open, the system should issue a warning.
- If the identification number is requested, the system should fail if the identification number entered is not in the correct format.
- If the name, surname and identification number on the official institution forms do not match, the system should fail.
- If a membership is to be created by uploading the photo, the system should fail if the uploaded photo exceeds the maximum size set for the photo.
- If the document is to be uploaded; If the uploaded document is not in the specified / requested format, the system should fail.
- If there is ReCAPTCHA verification, the system will fail with incorrect spelling/picture.
- If a previously blocked/restricted email wants to subscribe again, the system should fail.
- If there is no payment in paid subscriptions, the system should give a warning.
- If the first password and confirm password are requested while creating the password, if these two passwords do not match, the system should fail.
- If a password confirmation is required, the copy feature should not work for the first password entered.
- If the address is to be created in the form, the system should fail if characters other than the allowed special characters are typed.
- If the transaction will be made by entering the verification/activation code; If you are trying to verify the code that arrives after the specified time has expired, the system should fail.