Building a testing process for an e-commerce project (Magento 2)

Budget: 27000 UAH Deadline: 18 days

The benchmark for the first stage is 60,000 UAH and 14-18 working days. I would recommend Playwright with TypeScript - for Magento 2 this is a practical option for stable UI and E2E checks, parallel execution, error tracing, screenshots, and proper test support in the future.

In similar tasks, we have worked with e-commerce, marketplaces, complex order logic, catalogs, accounts, payments, integrations, and systems where process stability is important, not just a checkbox next to automated tests. Your proposal resonates with me because it concerns a foundation that can then be scaled - and it's better to design it properly once than to heroically patch tests after each release =)

> First stage of work
> audit of the current testing process and testing environment
> identification of critical user scenarios
> recommendation of the stack and architecture of the testing project
> setup of the automated test structure
> preparation of basic fixtures, configurations, test data, and reporting
> implementation of approximately 12-18 automated tests for authorization, catalog, search, product card, cart, checkout, and account
> documentation for launching, supporting, and developing

> Deliverables after the stage
> repository or separate branch with the configured testing project
> set of stable automated tests for key scenarios
> instruction for local and build execution
> description of the architecture, rules for adding tests, and working with test data
> brief audit report with risks and a plan for further expansion

Examples that are close in business logic
> https://business.ingello.com/prime-eva - e-commerce and complex processes around products, orders, and operational logic
> https://business.ingello.com/eva - retail, scaling digital processes, and a systematic approach
> https://business.ingello.com/vorfahr - automation and product logic, where supported architecture is important

Main profile for FLH - https://systems-fl.ingello.com/ua

To more accurately assess the first stage, two clarifications are needed.
> Is there a separate Magento 2 testing environment with test products, users, delivery, and payment without real charges?
> Is the checkout standard or are there custom modules, third-party payments, promo codes, bonuses, or non-standard checkout steps?

In general, a normal first stage can be done without unnecessary inflation - but the foundation must be laid carefully. As they say, measure seven times - cut once in the build. More precisely, in the build, it's better to run many times, but the idea is clear. Expand

Budget: 27000 UAH Deadline: 14 days

We have almost a ready foundation for this stage, it can be quickly adapted for Magento 2 and launch the first E2E checks, we can discuss it here on the marketplace, I am available ))

The benchmark for the first stage is 45,000 UAH and 10-14 working days.

I would recommend Playwright plus TypeScript. For your stage, this is more practical than a heavy overlay around Magento, as stable UI/E2E scenarios, video and crash tracing, parallel execution, a clear structure, and proper support after launch are needed.

In the first stage, I would include:
- a brief audit of the testing environment and current process
- a map of critical scenarios for the client side
- the structure of the automated testing project
- basic utilities, configurations, reports, local execution, and in CI if your pipeline is available
- 8-12 automated tests for authorization, catalog, search, product card, cart, checkout, and cabinet
- documentation for launching, support, and further development

After completion, you will receive a repository or branch with a test project, a set of ready checks, reporting, launch instructions, architecture description, and a coverage expansion plan.

From experience, we have e-commerce and complex systems with accounting, orders, and automation.
https://business.ingello.com/eva - close to e-commerce logic, catalogs, processes, and scaling.
https://business.ingello.com/prime-eva - a useful example for tasks where the reliability of the operational part is important.
https://systems-fl.ingello.com/ua - briefly about our approach for projects on Freelancehunt.

There are 2 questions to avoid guessing with coffee grounds =)
- Is there a separate Magento 2 testing stand with test payments, delivery, and stable test products?
- Which checkout scenarios are more critical for you - guest, registered user, different payment methods, promo codes, delivery?

If needed, we can conduct an audit and framework in the first week, and then gradually increase tests without pain, as a good foundation saves more than it costs later.
It sounds a bit bureaucratic, but here the architecture is indeed more important than the number of tests at the start; otherwise, automated tests quickly start breaking from every interface glitch.

We can also connect a light AI check for test crashes - for example, to have the system collect screenshots, errors, reasons for crashes, and provide a brief explanation for the developer or manager.
This does not replace the testing architecture but helps maintain coverage in long-term collaboration. Expand