Kazidomi

Challenge

Kazidomi turned to QAwerk to strengthen and extend their delivery team with professional QA and test automation engineers. Before our cooperation, they relied on bug reports from their customer care members, which often lacked the necessary details for developers to quickly understand the root cause of the issue.

The partnership with QAwerk aimed at achieving the following results:

• Faster bug fixing. Our task was to complete reports written by the internal team with pre-conditions, steps to reproduce the bug, and other details to save Kazidomi developers’ time and make it crystal clear what went wrong and under what exact circumstances.
• Automated testing. We needed to introduce test automation to reduce the time spent on functional, UI, and regression testing, which in turn leads to faster and smoother delivery of new capabilities to users.
• Improved conversion. QAwerk was responsible for paying utmost attention to the functionality directly impacting conversions. Our goal was to detect all possible conversion killers and ensure the user experiences no hiccups along their journey.

Creating and maintaining test documentation are an integral part of the quality assurance process, and that’s what we did for Kazidomi too. Each feature ready for testing required writing new test cases or updating the existing ones.

Solution

We believe rigorous testing is best achieved with manual and automated testing combined. With test automation, we increased the testing speed and achieved greater coverage. At the same time, manual testing allowed us to have that human touch and explore the platform from the user’s standpoint.

For a web solution like Kazidomi, these types of testing were essential:

• Functional Testing. We put maximum effort into testing most common user actions, such as authorizing, adding products to a cart, modifying cart contents, applying discount codes, among many others. We saw to it that every button, link, and filter serves its purpose and helps the user make a decision.
• Integration Testing. Bugs on a billing page are one of the most widespread conversion killers. Our QA engineers tested the integration with payment systems such as PayPal and Adyen to ensure the checkout is successful and stress-free.
• Cross Browser Testing. Multinational e-commerce platforms like Kazidomi have customers using different browsers on different devices. We made sure the user experience remains high quality regardless of the browser or device used. Automated testing focused on Chrome only.
• UI Testing. A sleek UI is no less important as impeccable app performance as it contributes to that first impression and building brand trust. Our QA team verified if the design implementation matches the requirements specifications.
• Regression Testing. Since Kazidomi ships updates frequently, the need in automating regression testing was apparent. With automated regression in place, bugs were reported timely, allowing Kazidomi developers to fix most critical issues before the release day and stick to their delivery plan.

We wrote 587 test cases from the ground up, among which 284 were automated.

Test Automation

All tests were executed on a server with a new database with no pre-created users or test data. The data was automatically created for each test case right before the test execution. This approach helped keep autotests stable and allowed running them in any order as there were no test data interdependencies. For example, if two test cases rely on the same piece of test data and the first test deletes it as one of the test case steps, the latter test will fail, resulting in a false positive.

Our autotests also contained post-conditions for data cleanup. When new data is generated for every small test case, the size of the data source explodes quite quickly, putting an unnecessary strain on the server. Therefore, each autotest deleted the test data it previously created after successful test execution.

As you can imagine, running 284 autotests simultaneously takes a while, or about 6 hours, to be more precise. To speed things up, we divided all the tests into groups, singling out the smoke group containing about 30 autotests for main product features. Other groups were labeled based on the functionality they checked, for example, “login”, “add to cart”, and “create account.”

These tests were run continuously after each commit to the GitLab repository. If needed, it was also possible to manually launch or skip autotests for a specific group.