The customer is the owner of a large US-based e-commerce solution specializing in selling natural foods, pet care goods, household cleaners, and other organic products.
As the customer’s business was growing fast, the following needs arose:
Considering the customer’s business needs, the following types of software testing were to be performed:
To face the challenge, a1qa was invited.
The a1qa engineers had the expertise to fulfill all testing tasks and prepared a detailed roadmap on how to allocate the client’s QA budget for the most effective results.
Both modules placed on frontend and backend parts were tested.
The solution client-side was responsible for user registration, catalog navigation, search and filters, adding products to the cart, promotional codes application, special offers, placing orders, payments, bonuses, and all kinds of notifications.
Backend functions included catalog and products settings, creation of marketing offers and discount terms, stock management, and many more.
The engineers tested both parts and revealed a large number of defects. Over 50% were of the major severity and higher and could have resulted in negative user experience after the release.
The most important issues were connected with the payment option and prices display.
As soon as the project initiated, the customer made a decision not to support IE 8 and outdated versions of other popular browsers.
The tests were performed in the latest versions of the following browsers:
To check the quality of the new design, it was decided to test the solution against four mobile devices (iPhone, iPad, Samsung Galaxy, Samsung Galaxy Tab).
The objectives of the solution performance testing were to:
During testing, all the tasks were fulfilled.
Upon the project completion, the customer was provided with the following test artifacts:
The customer had no QA processes in place, and the workflow had to be tuned up from scratch. Also, the development team disrupted the deadline, and the communication was hindered by the poorly collected and described functional requirements that had to be specified.
As a result, there was little time left for testing and software stabilization.
To assure the pre-release quality of the business critical functionality and fix the most serious defects, the team was expanded. The specialists were working extra hours and on weekends to complete testing on time.
Initially, the team was made up of 2 engineers and was further scaled up to 4 specialists (1 QA manager, 1 performance testing engineer, and 2 QA engineers).
Average experience in testing – 16 months.