If you are fortunate enough to be testing a new application without any existing data, you can fend off most phone number headaches by clearly establishing validation rules for phone number fields. The easiest type of validation is one that accepts ten digits only, and no other characters. The developer can rely on UI formatting to put the number in an easily-readable format rather than expecting the user to do it themselves. The reason why this is the best course of action is that allowing the user to add in formatting creates all sorts of ambiguity. If my phone number is 800-867-5309, how might I type that in? Just with dashes, or will I use parentheses, such as (800) 867-5309? What about the older format of 1-800-867-5309? With that format, I now have eleven digits.
Many developers try to accommodate all styles in the mistaken notion that this will make things easier for the user, but this actually makes things much more complicated. If both parentheses and dashes are allowed, there needs to be some sort of regex used for the validation. Otherwise, a user could type in something like ((800)--867 5309 and the number will be accepted. If the developer you are working with has decided that he or she would like to make it easy on the user by accepting parentheses and dashes, try entering values like 800--867--5309, 800(867)5309, and 8-0-0-867-5309. After you have demonstrated that it's possible to enter a badly formatted phone number, the developer's strategy may change.
As with Zip codes, it's important to consider how the phone number is saved to the database. The best strategy for US phone numbers is to strip out any formatting and save the number as just the ten digits. That way the number can be displayed in any way the UI designer deems appropriate.
Next, it's time to think about how bad phone numbers will be displayed to the user. If a number has been saved with formatting, will it be displayed with that formatting? Will some attempt be made to strip the formatting? Will it be displayed at all? I have seen all kinds of bad numbers in databases. One of my favorites was "dad's office number". No one can format that! A good strategy would be to format any ten-digit number by stripping out all of the non-number characters, and then adding in whatever format is desired for display. If the phone number is eleven digits and starts with a 1, the leading 1 could be stripped off and then the number could be formatted for display. With any other values, the "number" could be displayed as-is, or it could not be displayed at all. Whatever is decided, it's important to test with whatever bad numbers are currently in the database.
Another wrinkle not often considered is phone extensions. Many offices still use extensions to direct a call to a specific person. Sometimes phone fields allow extensions as part of the number, but this is a bad idea, for the same reasons that allowing the user to format their own number is a bad idea. Phone extensions can be any number of digits, so allowing them as part of the phone number means that now the validation can't expect a specific number of digits. Also, how might the user indicate that an extension is part of the number? Will they enter 800-867-5309 ext. 1234? 800-867-5309x1234? Allowing these types of variations will mean allowing letters and other characters, which it makes it more difficult to validate. A far better solution is to include a separate field for an extension. If your developer expresses interest in including the extension as part of the phone field, some testing with entries like 8008675309extextext...1234 will probably dissuade them.
Finally, remember to test editing phone numbers, especially numbers that are in an incorrect format. What will happen when the user has a phone number like 800-867-530 and tries to edit another field on the form? Will they be notified upon saving that the number is incorrect and needs fixing? This can be a good way to involve users in cleaning their own data. What should happen when the user tries to fix an invalid number? Ideally they should be able to save the value with a new valid number.
I hope that this post has emphasized the importance of having good phone field validation. If you are fortunate enough to be testing a brand-new application with an empty database, taking good care to ensure that only valid phone numbers are saved to the database, you will prevent many testing headaches in the future!
This post only tackled United States phone numbers. In my next post, I will take on the even greater challenge of international phone numbers!
As with Zip codes, it's important to consider how the phone number is saved to the database. The best strategy for US phone numbers is to strip out any formatting and save the number as just the ten digits. That way the number can be displayed in any way the UI designer deems appropriate.
Next, it's time to think about how bad phone numbers will be displayed to the user. If a number has been saved with formatting, will it be displayed with that formatting? Will some attempt be made to strip the formatting? Will it be displayed at all? I have seen all kinds of bad numbers in databases. One of my favorites was "dad's office number". No one can format that! A good strategy would be to format any ten-digit number by stripping out all of the non-number characters, and then adding in whatever format is desired for display. If the phone number is eleven digits and starts with a 1, the leading 1 could be stripped off and then the number could be formatted for display. With any other values, the "number" could be displayed as-is, or it could not be displayed at all. Whatever is decided, it's important to test with whatever bad numbers are currently in the database.
Another wrinkle not often considered is phone extensions. Many offices still use extensions to direct a call to a specific person. Sometimes phone fields allow extensions as part of the number, but this is a bad idea, for the same reasons that allowing the user to format their own number is a bad idea. Phone extensions can be any number of digits, so allowing them as part of the phone number means that now the validation can't expect a specific number of digits. Also, how might the user indicate that an extension is part of the number? Will they enter 800-867-5309 ext. 1234? 800-867-5309x1234? Allowing these types of variations will mean allowing letters and other characters, which it makes it more difficult to validate. A far better solution is to include a separate field for an extension. If your developer expresses interest in including the extension as part of the phone field, some testing with entries like 8008675309extextext...1234 will probably dissuade them.
Finally, remember to test editing phone numbers, especially numbers that are in an incorrect format. What will happen when the user has a phone number like 800-867-530 and tries to edit another field on the form? Will they be notified upon saving that the number is incorrect and needs fixing? This can be a good way to involve users in cleaning their own data. What should happen when the user tries to fix an invalid number? Ideally they should be able to save the value with a new valid number.
I hope that this post has emphasized the importance of having good phone field validation. If you are fortunate enough to be testing a brand-new application with an empty database, taking good care to ensure that only valid phone numbers are saved to the database, you will prevent many testing headaches in the future!
This post only tackled United States phone numbers. In my next post, I will take on the even greater challenge of international phone numbers!
No comments:
Post a Comment