Test cases of ecommerce websites can be considered as a list of instances or fields that a tester will use to determine whether an ecommerce website under test satisfies the requirements or works appropriately.
To optimize customer experience, any ecommerce website needs to be functional and accessible. Therefore, an ecommerce website usually is tested in terms of usability, functionality, performance. Because there are many pages, functions on the website, without a test case, there is much likelihood that essential fields are missed.
For these reasons, ecommerce site test cases are one of the beneficial support for ecommerce website testers. However, not everyone knows what a full site testing for an ecommerce website should be. Therefore, we have noted down must-have test cases for your ecommerce site that may be helpful for you here.
Firstly, to start any testing package for your ecommerce website, it’s crucial to have a report on what you test. Any ecommerce website test script includes seemingly endless points to check. Therefore, it may take you days to find out what you have left if you miss a minor point. Plus, a bright and well-structured report will be much easier to follow in the next time and for other readers.
Test case management tools such as Quality Center, JIRA have become well-known for many companies to write test cases for an ecommerce site. Some are using excel sheets to write to them. However, they all share several standard must-have information.
A- Test case template for ecommerce website
- Project name: this is the identification of each project to others. In case you carry out several tests, those tests should be named following uniform rules.
- Test ID: Each test project for any ecommerce website contains many criteria. Therefore, to make sure that you can quickly check or mention a single test case, each should be given a unique ID.
- Date: This should be the date when the test was created.
- Section: There are many sections on each page ecommerce website. To not miss any part, you should write down which section you are testing. For example, on the product page, you must test sections such as product images, product information, product descriptions, product reviews,…
- Test steps: all test steps should be mentioned in detail here.
- Expected result: This is the result which we expect on testing or, in other words, how the system shows when this section works appropriately.
- Actual result: These are the results that the system shows on being tested.
- Status: If the actual test result is similar to the expected result, the status should be marked as “passed”; otherwise, it will be marked as “failed.” In case that testers need to investigate more, mark the status as “pending.”
In case the test is carried out in different devices such as desktop, mobile, and tablet, make sure that you test and mention all the results in each device.
A sample for the report for your reference:
B- Test cases for ecommerce website
For your simple measure, a full-site test case for an ecommerce website will include every page shown on the website. A typically online customer may start experiencing his online purchasing journey with the homepage, spend his time on several CMS pages, and finish with the check out page. Therefore, to make sure that you miss a single page, list all pages first as the sections before going to the details.
Here are the test cases of some main pages that you won’t want to miss out. There are three most important pages that we list details: homepage, category page, and product page.
The homepage is usually the start of the customer journey on any ecommerce website. So make sure that it bangs on your customers from the very first moment.
The checklist on this page includes:
- Display: There are endless styles for eCommerce sites, so it’s impossible to stick and follow display rules. But you should test if elements such as font type and size, colors, icon styles,…are functional.
- Banner: Normally, there are hero images or banners at the top of the homepage.
In the banner, the tester must test:
- Display: test all elements – there may be image, title, description, buttons,… in the banner;
- Buttons: Do buttons’ colors change on being hovered or clicked? What will happen when each button is clicked? Is it taking to the right page or right deal?
- Block: this should be tested as the banner in the display, buttons.
Check out Top 7 Magento 2 Banner Slider Extensions
2. Category page
There are two types of category pages, including landing page and listing page.
- Landing page: this page will show you an overview of any category. There are some normally displayed fields on this page, such as category description, details, list of subcategories,…
The landing category page should be tested as the homepage in the images, display, buttons.
- Listing page: The listing page is more used than the landing category page. It shows products that belong to the category or subcategory. The search page is also considered as a listing page.
There are many test cases on the listing page to test:
To start, each listing page, due to its functionality, contains many products. We must test the display of the products, including:
- Display: What will show in each product cell when we hover on or not hover on?
- Buttons: Are the buttons or icons shown in the right place? Do their color change on being hovered or clicked? What will be shown in each product cell on being hovered on or not hovered on?
To test the listing page navigation, there are several test cases for your ecommerce website:
- Subcategory: In this field, the tester must test if the list of subcategories is enough. Another area is whether each subcategory link is clickable and directs to the right page.
- Filter: how is the filter displayed (by a bar, range, enter data, checkbox,…)? How to remove selected filters? Is the removal selection work appropriately?
- Sort-by: How is the sort-by function displayed? What is the default sort-logic? Check the list of sort-by logic and their function if each sort-by logic works appropriately?
- Pagination: How is the pagination displayed? How many products are displayed on each listing page? Does the listing page have infinite scroll functionality?
- Blocks: this section can be tested as the homepage.
- Wishlist block: How is this block displayed? Does each product link in this block work? Can the products in the wishlist block be added to the cart? Can and how can the products here be removed? Please note that to test this function, the tester must login.
- Compare block: How is it displayed? Does the product link directly to the right product page? How are the selected products removed in this block? Does the compare function work appropriately?
3. Product page
- Product type: It’s necessary to check the product type because different product types may be suitable for different display layout.
- Product images: Both the main image and the slider images should be tested. Are they the right pictures of the product? How can customers switch images (by clicking on the other image or by clicking on the arrow,…)?
- Product information
- How is the product information displayed and the function when it is in stock? This is very important in any test case of the ecommerce website because the functionality here directly affects the customer to add to cart.
- How is the product information displayed and the function when it is out of stock? There are some store owners choosing the product information to disappear when it is out of stock; some, on the other hand, let the product still be shown. This case may lead to other functions such as back-order or product in-stock alerts,… Therefore, make sure that all the cases are tested.
- Product details or description: This should be checked for all elements, including text font, size, and spelling.
- Product reviews: How are customer reviews shown on the product page? How can a customer submit a review?
4. My account page
My account page contains all information about the customer. There are several functions that every customer may experience at least once, such as change, and add their address or contact information or checking order status. Each function must be listed as a test case.
5. Cart page
A cart page is an essential part of an e-commerce website. It is the page where customer can add their wanted items and simply checkout. To start your test case of the cart page, check every element such as product, quantity, and functionality such as change the quantity or remove a product from the cart.
6. Checkout page
Because customer checking out on your website may register an account or not. So your test cases must cover both scenes.
7. CMS page
Test cases for each page include display and links (see if the attached links in each page are direct to the right page or form)
8. Other functions
Pop-up: Pop-up – with its effectiveness in compelling attention from users – are popularly used in many ecommerce websites. If your websites use this tool, don’t forget to add it to the full-site test cases. Test cases for pop-up will also include:
Create attractive Pop-ups for your Magento website with Magento 2 Pop-up
There are still some other cases to be tested, such as the back-end and the API testing; we will keep updating them. About the front-end test case, have we missed any cases? Contact us and let us hear your opinion.
In case you need to test your full ecommerce site, LEAVE HERE Your Personalized Testing Requests to get a FREE CONSULTATION!