Building a QA process and test automation for Magento 2

Budget: 6000 UAH Deadline: 7 days

Good day, Anastasia.

To be honest about Magento 2 right away, since you ask for experience: I have worked with the frontend of the Magento 2 theme (Amasty, RTL version), but I won’t pretend that I have a full cycle of QA specifically on Magento. My profile is automation and process building: Playwright and Puppeteer in production, dozens of standalone systems on VPS around the clock, with logging, alerts, and self-restarting.

Why this is relevant here. At the first stage, you are asking not for automated tests, but for a process. And the process breaks not where there are few tests, but where the tests are unstable and are no longer trusted. In e-commerce, this is almost always the checkout: asynchronous cart recalculations, delivery, payment redirect.

What I will do at the first stage:
1. Audit of the current process: what is being tested now, by whom, when, and what regularly breaks into production.
2. Risk map for business processes (catalog, search, product card, cart, checkout, authorization, cabinet) — using the formula "probability of failure × cost of failure". Checkout almost always comes first, and that’s where we start.
3. Separation: what remains manual (design, layout on real devices, one-time promotions), what we automate (regression of critical scenarios, smoke tests after deployment).
4. Stack: Playwright + TypeScript, Page Object, isolated test data, run in CI on each deployment. I will justify why not Selenium and not Cypress specifically for your case.
5. Implementation plan in stages, with estimates of timelines, budget, and costs for further support.

The main thing I will provide beyond the technical specifications: a criterion by which you will understand that automation is working. It’s not the number of tests, but the share of releases where a test failed and it turned out to be a real failure, not a flak.

The price for the first stage (audit + risk map + stack + implementation plan with estimates): 6000 UAH, 7 working days.

Examples of work: guardlabs.online/studio

If you need a deep Magento expert with experience in their specifics — just say so, I won’t insist. If you need someone who will build the process and won’t give you a hundred unstable tests — I’m ready to start. Expand

Budget: 27000 UAH Deadline: 14 days

The Magento 2 platform operates at the level of e-commerce logic - catalog, product card, cart, order processing, personal cabinet, payment integrations, and inventory balances. For the first stage, I would allocate 10-14 working days and a budget starting from 48,000 UAH for the audit, risk map, prioritization of UI/E2E scenarios, automation stack, and implementation plan.

I would recommend Playwright - it is more stable for modern stores, works better with parallelism, tracing, video recording of failures, and checks in different browsers. Cypress is also fine, but for long-term e-commerce automation, I would say Playwright causes less pain in maintenance. Selenium usually only makes sense if there is already a legacy or specific infrastructure.

> Stage 1 - audit of the current process, risks, and critical scenarios
> Stage 2 - matrix of manual and automated testing
> Stage 3 - design of the structure of automated tests, test data, reporting, and launches
> Stage 4 - implementation plan, assessment of support budget and scaling

A QA Lead should work on the architecture of the process and an Automation QA Engineer for the technical verification of the approach. If we proceed to implementation after the audit, we can start with a small core of tests for order processing, authorization, cart, and personal cabinet. Not everything that moves is worth automating - an old wisdom, but it is quite relevant here =)

Access to the test environment will be needed, a description of user roles, examples of typical orders, a list of critical Magento 2 modules, and current bug reports or checklists, if available.

I would like to clarify two points:
> Is there a separate staging environment with test payments and test accounts?
> Is it necessary in the first stage to only design the automation, or also to create a small technical prototype for 3-5 scenarios?

Similar examples:
> https://business.ingello.com/prime-eva - e-commerce and systemic work with retail logic
> https://business.ingello.com/eva - large retail, where stability of processes and scaling are important
> https://business.ingello.com/vorfahr - automation of processes and complex product logic, relevant to future scaling

The main page of Ingello for the exchange - https://systems-fl.ingello.com/ua Expand

Budget: 15000 UAH Deadline: 21 days

I have been involved in test automation for over 10 years, including experience with PHP, and I have also worked on development with Magento (I have completed projects on freelancehunt). I will build you a basic turnkey automation solution in a short time, with further development if necessary.

Budget: 18000 UAH Deadline: 12 days

Good day! I work with QA automation in e-commerce, including UI/E2E. For your Magento 2, I will conduct an audit of the current process, highlight critical scenarios (catalog, search, product card, cart, checkout, authorization) using a risk-based approach, and differentiate between manual and automated testing. I will propose a stack (leaning towards Playwright + TypeScript + CI) and an implementation plan with an assessment of timelines and budget for further support. At the end of the first stage, you will receive a document with the strategy + pilot automated tests for 2-3 key scenarios.

Budget: 25000 UAH Deadline: 30 days

Good day!

I have about 10 years of experience in software testing (web, API, mobile). I have worked with functional, regression, UI, and API testing, as well as integration testing.

I have experience testing mobile applications (Android and iOS) and my own set of testing devices. I also have experience testing microservices architecture, integrations, and asynchronous systems (RabbitMQ). In my work, I use Postman, Fiddler, Docker, Git, SQL, as well as monitoring systems (Kibana, Grafana) and CI/CD (GitLab CI).

I also have about a year of experience in AI automation. Here are a few examples of workflows I recently created:
- Telegram news channel with AI message processing
- Chatbots for support
- Creating a knowledge base for the company
- Various automations specifically for QA (creating cases with subsequent analysis and documentation, automating work with databases, etc.)

Recently, I have worked on projects:

• https://sqlbackupandftp.com / https://sqlbak.com — database backup automation services.

• https://expofp.com — SaaS platform for event planning and management.

• https://lunu.io — blockchain project, cryptocurrency payment gateway, and Web3 payment ecosystem.

I would be happy to share more about my experience.

https://qanetix.com Expand

Budget: 1234 UAH Deadline: 1 day

Good day! I have experience in QA processes and test automation. Please write to me privately, and we will discuss the details.

Budget: 27000 UAH Deadline: 10 days

We already have an almost ready solution for the QA process and UI/E2E automation of e-commerce, which can be quickly adapted for Magento 2 and launched in the first phase =)
We have relevant experience with e-commerce, marketplace projects, personal accounts, carts, checkout, payments, roles, and scenarios where stability after releases is crucial.

For the stack, I would recommend Playwright + TypeScript as the base for UI/E2E, as it handles modern frontends well, supports parallel runs, browser isolation, and convenient crash diagnostics.
Cypress can also be considered, but for Magento 2 and complex checkout scenarios, Playwright is usually more practical.
I would only use Selenium if you already have an internal legacy on it.

The benchmark for the first phase is 45,000 UAH and 10 working days.
This phase includes an audit of the current QA, a risk map, a list of critical scenarios, separation of manual and automated testing, an automation plan, stack, budget for the next phase, and preparation of a pilot test structure.
A QA Lead + Automation QA Engineer will work on this, and if necessary, we will involve an architect for integrations and CI.

Important clarifications before an accurate estimate:
> Is there currently a test or staging site with separate payment methods and test accounts?
> Which integrations are the most critical for checkout - payments, delivery, promo codes, inventory, ERP, or CRM?

Similar examples from Ingello:
> https://business.ingello.com/eva - e-commerce and complex processes around sales, catalog, and operations
> https://business.ingello.com/prime-eva - automation and systematic work with retail processes
> https://business.ingello.com/carveli - an example of an e-commerce approach where catalog, orders, and user journey stability are important

Main page for the exchange:
https://systems-fl.ingello.com/ua

!!In the first phase, it’s better not to write many automated tests randomly, but first cut critical scenarios from secondary ones!!
Measure seven times - automate once, this works almost literally here. Expand

Budget: 25000 UAH Deadline: 25 days

Good day!

I have experience in building and automating testing for web and mobile projects. I have not worked much with Magento 2, but I am well acquainted with e-commerce principles and typical business processes: product catalog, search, cart, order placement, authorization, personal account, payment scenarios.

In similar projects, I have tested various online stores, web services, and internal CRMs. I have also worked on automating mobile Android applications using AutoX.js and Appium, automating user scenarios, form validations, authorization, navigation, message handling, and repetitive actions. For web projects, I used Go-Playwright, Selenium, and Puppeteer for automating E2E scenarios and regression testing.

For a new project, I would recommend Playwright. It is fast, stable, supports all modern browsers, works well with parallel test execution, has convenient reporting, and is less demanding in terms of maintenance compared to Selenium. If the project has specific requirements, the stack can be discussed separately.

I usually structure the process as follows:

* first, an audit of the current testing process;
* identification of critical business scenarios and risks;
* distribution of what should remain for manual testing and what to automate;
* preparation of the test automation structure;
* gradual implementation of automation, starting with the most important scenarios;
* integration of test execution into CI/CD and ongoing support.

I usually conduct an assessment of the work after a brief introduction to the project. First, the audit is evaluated, then a list of scenarios for automation is formed, after which timelines, budget, and implementation plan can be determined quite accurately.

I can personally work on the project as an Automation QA Engineer. If necessary, it is possible to scale the work and involve additional specialists.

I would be happy to discuss the project details and propose an optimal automation implementation plan. Expand

Budget: 27000 UAH Deadline: 14 days

Good day. I can help build a QA process and E2E automation for Magento 2.

I have practical experience in Magento 2 projects with large catalogs, custom product cards, and complex order checkout flows. I take a comprehensive approach: auditing the current process, risk analysis, identifying critical scenarios, and prioritizing for manual and automated testing. For UI/E2E, I usually recommend Playwright due to the stability of parallel runs, cross-browser compatibility, and easy integration into CI. I implement the process in stages, starting with a quick audit, launching an MVP set of tests for critical business scenarios, and gradually increasing coverage. I assess the work based on the level of Magento customization, the number of critical scenarios, and the state of the testing environment. The project will involve a QA Lead for auditing and strategy, Automation QA for writing E2E tests and setting up CI, and Manual QA for checking scenarios and preparing test data. An important technical detail: a stable staging environment with reproducible test data and access to logs and APIs is required.

Do you have access to staging with test data for the initial audit?