Test Objectives for Email Addresses

Email Address Test Objectives

The email address field is probably the most common element on most web interfaces these days. This humble text field usually has no other additional visual indicators except something to encourage to fill in your email address. But the amount of test objectives this common user interface element holds is huge.

email address

Let’s have a look at few examples below. List has valid email addresses in the group Valid, but also few examples that technically are valid also as those match RFC5322.

Group Test Objective
valid first.mid.last@name.com
valid first+last@name.com
valid “first@last”@names.com
valid %first#mid&last@names.com
valid {first-last}@names.com
valid %first#mid&last@names.com
valid first_last@[127.0.0.1]
valid first.last@localhost
valid first_last@relative-names.com
valid _@names.com
valid {!$&*?}@names.com
technically first_last@1.com
technically _______@_______.com
technically first_last@[192.0.1.100]
technically first_last@127.0.0.1
technically first_last@127.0.0.1/8
technically first_last@[2001:db8:85a3::8a2e:370:7334]
technically first_last@[2001:0db8:85a3:0000:0000:8a2e:0370:7334]

If you have other good #TestObjectives for email address fields please comment below.

And as per with any other testing there is always another angle to look at. We know that testing is rarely over, if time permits there is always something more to test. So with Exploratory Testing its important to set your time boundaries in place. Similarly testers should also remember that commonly for one positive test case there is often 3-5 negative test cases.  Looking at the list above which has 18 #TestObjectives listed, so most likely there 50 to 90 negative #TestObjectives to consider.

Click below to get an eBook with further reading about Test Objectives.

Read more about test objectives

 

 

 

Facebooktwittergoogle_pluspinterestlinkedinmailby feather

Leave a Comment

Your email address will not be published. Required fields are marked *