With $50 billion+ in gross transactions, more and more businesses are relying on Magento. Testing an e-commerce site is not the same as testing a content oriented website. It is important to understand the retail and online business to test an e-commerce site. In this article, we would in particular be covering the different aspects of Magento QA Testing.
Magento QA Testing: Categorized by pages
Unlike a content site, an ecommerce site has many different pages. These entail the following. While undertaking our QA process, we consider the following pages:
Home – The Index page is the storefront of your online business and welcomes your customers into your business by providing them with information about your business and links to second level pages.
Category Overview – Landing page for overall categories like Men or Women clothing, outerwear, etc. If your business has only one category of product this page will be replaced with the Category Page.
Category Page – This page is the list view for the products under specific categories. The focus here is to allow the customer to browse the products in order to select one or more to peruse.
Product Page – Brings information about the individual product with the main call to action “add to cart” button.
Search & Search Results – E-commerce websites need search functionality for those customers who do not want to wade through all the pages to get what they want.
Login/Create Account – Returning customers like to have information kept on them for easier ordering. The account is also a great way to provide reward/loyalty points management.
Cart – The cart is where your customer selects what they want to purchase. If you use promo codes this is a good place to put them and also show shipping costs to their location.
Guest Checkout – Some customers do not like information stored. Allow them to enter their information as a guest but invite them to create an account.
My Order – Order history in the account allows the customer to go back and reorder an item purchased in the past, to change an order, or to cancel an order.
Returns – The best return pages lay out the return/exchange process in an easy to understand way.
Store Locator – Some of your customers will come to your page just to find the nearest store to them.
Feedback – Encourage users to share their feedback about the website or products.
Our team regularly works with the Magento Functional testing framework. Keeping this in mind, we have listed out our eCommerce test plan pertaining to Magento in particular:
Magento QA Testing – Best Practices
When initiating testing in Magento e-commerce, we need to follow procedural testing and prepare a test case document which covers
- Functional test scenarios
- Admin test scenarios
- Custom modules in the website
We should execute all the test cases in three environments viz QA, UAT and Production to have flawless user experience on the live website.
Key Testing Methods
Here are the main categories of testing methods that we use for Magento:
Magento Functional Testing
Execute the test case document to check whether all the functionalities are working fine after every release and new security patch implementations. Whenever a new functionality is added to the website test cases should be updated.
Gather the supported device list from the business owners before beginning responsive testing. When converting a website to a responsive platform, prepare a separate test case document for responsive testing.
Verify the critical business scenarios, designs and CMS pages in supported Windows and Mac environment browsers.
The website should be load tested before any major release to make sure the reliability of the application/servers.
Third Party Integration Testing
The e-commerce application using any third party tool for customized modules like Payment, Gift Card, Shipping, Search and SEO should be tested to ensure the communication of data flows without any issues.
When the application is stable, go ahead with framing automation scripts for regression testing. This can be done by Magento inbuilt Magento Test Automation Framework.
Automation of regression testing will ensure the application is of high quality. It also reduces the regression testing time.
Checklist For Testing Magento Admin:
What we test?
We provide a comprehensive list of Magento solutions and set a special security environment for tje monitoring system operation, we assess the integration of a store with third-party services, such as Instagram, Google Analytics and others. Also, we test Magento integration with various system types: ERP, CRM, POS, Payment Gateways, Email Marketing. Here is an indepth look into our Magento 2 checklist:
Verify the following key items:
- Admin login
- Create Account via back end
- Reset password
- Email notification for user registration, order confirmation, Forgot password etc.
- Edit/Remove cart items
- Shipping method quotes
- Checkout flow as registered user/specific custom group.
- Create order via back end
- Promotion rules testing
- Catalog price rules
- Shopping cart price rules
- Custom modules verification
- Third party modules integration
- CMS pages/blocks
- Email Subscription.
QA Best Practices: In a nutshell
QA testing best practices:
- Test one thing at a time: tests should have clear objectives. Each test should focus on a feature or look at things like user interface or security.
- Use regression tests: testing a main feature once isn’t enough. New additions to the code repository can interfere with features that previously passed tests.
- Report and track bugs: determine how bugs will be reported and what kind of data is needed. Choose a bug tracking tool adapted to your workflow and determine which QA metrics will be tracked.
- Leverage analytics: keep records of every test conducted and use this data to determine where bugs are likely to occur. This data will help you to develop new tests that address problem areas.
- Choose the right environment for tests: try covering a wide range of scenarios, including different devices, OS and user profiles.
- Use unit and integration tests: unit tests will isolate each component of your app, while integration tests will assess how well each subsystem works. Run unit tests in parallel to save time, but don’t move onto integration tests until you have ensured that individual components work like they should.
- Don’t neglect the UI: use functional tests performed by human testers to perform end-to-end scenarios and get a feel for the UI of the app. It might be best to wait until you have fixed issues detected during unit and integration tests.
Following the best practices of QA reduces cost in terms of unnecessary re-work. A well-tested e-commerce site increases average order value, optimizes checkout and makes shopping a delightful experience for the customer.
Hope the article helped to better your understanding on Magento QA.
Author’s Note: This blog has been originally published on February 1, 2016 and updated on June 22, 2020.
We care about the quality of your Magento store. Let us help you out with our Magento QA services to improve your business.