Basic Points to Test an E-Commerce Website

E-commerce testing involves testing high value, high risk and high performance business critical systems. The cost of a failure in an e-commerce system is hence formidable and generally the testing process involves considerable effort in designing and integrating an effective risk management process into the testing to avoid or minimize the cost of failures.

A bug in an underlying specific component such as webserver, transaction server or database system might be missed or ignored because the focus of testing is basically done based on the code written for the web application. Unfortunately, a least concerned bug in a third-party component might cause a serious failure when the system is in production, leading to bad publicity, loss of customer confidence, and revenue.

Here are some basic points that should be taken into consideration while testing an e-commerce site:

a. Payment System:

This is the crucial part of an e-commerce website, however when testing payments, testers like to test the clear scenarios of adding an item to the basket, inputting your details and going through with the checkout. But that doesn’t test the negative sides, can you resume the checkout after pressing the home button, is the URL tamper able to order more items than you are paying for? You may also want to try to submit duplicate payments, use invalid credit card numbers and exceed limits.

b. Product Pricing:

Sometimes companies add special offers in prices for some items, and these special dealings are common faults in the pricing system most of the times. If there is a discounted price for an item that care should be taken that the discounted price is calculated throughout the process till the checkout is completed. Even simple things like vouchers, coupons, gift cards calculation when involved, these can put severe impact in the usability of the application.

c. Data Import Testing:

Some applications that have data fields that handle product details and customer details care should be taken for them while importing data to the application regarding mandatory fields, special characters, duplicate data, validations of fields.

d. Web Browser Compatibility:

Before starting the test, the customer using the application should be taken into consideration, and accordingly as per the specifications testing in different browsers should be done, because testing in all the browsers is impossible in one go. However as per the usability, testing in multiple browser gives an idea about the key platform related issues.

e. Device Compatibility:

In the same way as browser compatibility the targeted audience should be considered before deciding the device and operating system in which testing is to be performed, as testing using all combinations of devices and operating system is next to impossible, however care should be taken about the most common device and operating system in which the application will be frequently used as per the user.

There are a number of key areas which should be considered while testing an e-commerce site. The above mentioned points are just guidelines that should be taken care of while testing an e-commerce site. Of-course the risk and requirements will differ from business to business but these are the basic points that can be considered while testing an e-commerce site as a beginner. Learning and exploring will provide a lot more ways of testing.

So keep learning… Happy Testing… 🙂


Written By: – Smita Dash, QA Engineer, Mindfire Solutions


Posted on April 9, 2014, in Agile Testing, Enterprise Application Testing, Manual Testing and tagged , , , , , , , , . Bookmark the permalink. Leave a comment.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: