Mobile, Web and Custom Software



In most of the online and mobile applications, verifying Email feature is considered collectively of the most vital components of testing, to assure quality in Email element further along with alternative parts of the system.
Emails triggered under totally different scenarios are thought to be valid by checking for all its parts which have a model of Email, Links/buttons within the Email, From, To, Cc, Bcc fields, Attachments, Content as per Email notification, etc.


Each element within the system (Web/Mobile applications) might have completely different functions to send Emails. Integration between the parts and Email plays an important role in reaching end-user with correct notifications. Any negligence after wear confirmation this feature can cause misunderstandings, unhealthy name on the purchasers, hacking, etc.


Validation points in testing Emails varies from kind to kind, and once more from application to application. Ordinarily, all Emails ought to be valid for the example (which includes application emblem, application name, Addressing the user, Footer contents — Copyright, client support details), date and time stamp for various time zones.
Here discuss some common kinds of Email that nearly everyone seems to be responsive to (all the validation points given below are the essential certify the tester must perform whereas testing Emails of the application).


When a user registers to an application for the first time, he/she must activate the account by clicking on the activation link sent in Email. This also verifies the user’s given Email address is valid and accessible.
Validation points are as below:
• Activation Link or button — clicking on it should:
• Take the user to respective application’s page with user account logged in
• User’s Email account should get verified automatically if the application page is reached successfully through Email
• Duration — Check for the duration within which the link has to be clicked and verified.
• Verify within the specified duration
• Try to verify after the duration has passed — Account should not be activated and Email should remain unverified.


Validation points are as below:
Reset password link
• Clicking on it should take the user to various application’s page to reset the password
• Some applications can raise user to answer security question before displaying reset password page, and a few can have security question integrated with reset password page itself, and a few won’t have this feature at all
• If user resets the password with success, the link within the Forgot password Email that has been received should get deactivated and non-functional
• If user cancels the reset password flow, the link in the Forgot password Email that has been received should stay activated
• Duration — Check for the duration within which the link has to be clicked for password reset
• Click on the link and reset password successfully within specified duration
• Try to click on the link after the duration has passed — Link should be deactivated and invalid.


This is to inform the user about the action to require in a specific range of days. This is sometimes that the bill payments, taking action on unfinished things (example: accepting or rejecting the invite to some event in a specific range of days, submitting forms, etc.)
Validation points are as below:
Number of due days/Due date
• If email notifies a couple of range of due days then the amount should be either zero or additional, zero days meant to be the present date the due is. It should not be in negative numbers. If email notifies a couple of due dates (Calendar date) then the date should be either the present one or the longer term.
Type of action
• Check what is the sort of action needed. It should very clearly state what kind of action that user has to take. Be it the bill payment, submissions, feedback, etc.


This is to tell the user about date has passed. This is usually to inform the user that he/she has not taken action on the things within date.
Number of overdue days
• Check that the number of overdue days should be either one or more. It should never be zero or negative numbers
• Few applications can have the availability to customize overdue emails to be sent daily/weekly/ monthly, once due date has passed, till the user completes the action. Few applications can have the standard notification to be sent just once only when the due date has passed.


This varies as per user needs. The user will choose one in every of the following Daily, Weekly, Bi- Monthly or Monthly subscriptions. This can typically be for newsletters, updates, offers, etc.
• Emails ought to be sent as per user choice for a subscription. If Daily, then subscription email ought to be sent only once in a very day. If weekly, then once in a very week. And goes on…
• any links within the email should navigate to the application’s individual page. If the e-mail is for updates, then the link should redirect to the page wherever updates square measure meant to be displayed. If the e-mail is for offers, then the link should redirect to the Offers page of the appliance. It depends on the kind of subscription user has selected.


Emails here intends user to supply feedback through forms/link to forms. Validation points are as below:
• Link within the email should send the user to kind submission page of the appliance as per the kind of form user is needed to submit
• Once submitted, clicking on the link once more should apprise the user that type has already been submitted. It mustn’t permit the user to re-submit the form.


Here are to notify the user about the confirmation of the action taken. This is usually the reservation confirmations, order confirmations, query confirmations, etc.
Validation points are as below:
Confirmation details:
• Order range/booking number ought to be correct and match the amount displayed in application UI. Because it is that the symbol to trace the orders/bookings, it should be unique (to be validated in backed — DB) throughout the application. No orders/booking ought to share constant symbol.
• Along with the amount, it ought to even be valid for the kind of order, user info, request address, shipping address, and price. All the knowledge should be exactly similar to what user has provided in the application UI.
• A link within the email ought to take a user to the order’s details page in application UI. There should be exact match between information in Email and application UI


Here, a user receives the complete chat transcript as Email. This is sometimes once the Live Chat with client support is finished.
Validation points are as below:
• Check for the name of the one that provided online support. Make sure the complete chat is a gift within the email with sender’s details for every chat entry (Person name, Date and time the chat message was sent, etc.)


The user receives Emails with attachment. Attachments will be password protected/unprotected. This typically is the statements from financial domains, end user License Agreement for reference, Terms & Conditions for reference, etc., this again varies from application to application.
Validation points are as below:
• Type of the attachment
• Valid file types should be sent as an attachment. All the attachments being opened should be virus scanned before downloading/opening. This again will be customized at application level at the backend, like, virus scan to be performed only downloading, only if opening, for each downloading and opening.
• Password protected attachments should transfer while not requesting the password. However while opening it either from Email itself or opening the downloaded copy should ask for the password.

Leave a comment

Your e-mail address will not be published.

Enjoy this blog? Please spread the word :)