Comprehensive E2E Testing for Your 1C-Bitrix Store

Imagine deploying a new release, only to discover next that the cart fails to apply a discount when product quantity changes. This scenario happens often. According to industry research, automated testing can reduce support costs by 40%. Over 8 years, we have audited more than 150 Bitrix sites. Without a structured test plan broken into modules, such defects slip through—particularly in edge cases. Our solution: test each module in isolation and together. This approach can cut support costs by 40% by catching issues early. Order a test run and receive a report with actionable insights.

Automated regression testing is 4 times more efficient than manual regression testing. Our clients save an average of $5,000 per year on support costs.

Why functional testing matters for Bitrix

Bitrix is a multifaceted platform; a bug in one module can ripple to others. For instance, a faulty infoblock query may duplicate products in listings. A broken order event can prevent email confirmations. Manual checks without a plan often miss these. After editing product properties, you must rebuild the facet index—a common pitfall. Automation minimizes human mistakes and accelerates regression by 3x.

Our expertise & track record

With 8 years of QA experience and over 150 Bitrix projects, our team is certified in Bitrix development and testing. We guarantee at least 90% test coverage for critical flows. Our clients report a 40% reduction in support tickets after the first automated test run.

Modules we examine

Catalog and infoblocks (iblock)

• Filtering by properties: ensuring IBLOCK_PROPERTY values work correctly with empty (null) values.
• Faceted search: null entries return unexpected results? We verify.
• Pagination and sorting accuracy.
• Duplicate product detection: null data should not appear.
• Image and file uploads: null case handling.

Cart and checkout (sale)

• Add, update, remove items: quantity changes recalculate totals, including null discount scenarios.
• Coupon codes: apply invalid or empty codes gracefully.
• Shipping options: null selection behavior.
• Payment processing: null payment method error handling.
• Order placement: ensure all steps complete, even with null values.

Personal account (cabinet)

• Login/logout flows.
• Profile updates: save empty fields.
• Order history display when no orders exist.
• Password reset: handle empty inputs.

Integrations

• 1C exchange: data sync with null entries.
• Payment gateways: response parsing when null fields are sent.
• Delivery APIs: null address validation.

How we deliver results (step-by-step)

1. Initial audit: Review your Bitrix setup and identify high-risk areas.
2. Test plan creation: Write detailed test cases for each module.
3. Automation development: Build Playwright scripts for e2e flows.
4. Test execution: Run tests across environments and record outcomes.
5. Bug reporting: Provide prioritized bug list with logs, screenshots, and fix recommendations.
6. Retest: After fixes, rerun tests to verify closure.

Comparison: Manual vs Automated testing

What you get (deliverables)

• Detailed test plan document.
• Automated test scripts (Playwright) compatible with your CI.
• Bug report with severity, logs, screenshots, and fix suggestions.
• Retest report after corrections.
• One month of post-launch support and test maintenance.

Pricing examples

• Small store (<100 items, basic integrations): $800 – $1,500
• Medium store (100-500 items, few modules): $2,000 – $4,000
• Large store (500+ items, many integrations): $5,000 – $10,000

Frequently asked questions

How much does automated testing cost?

Project costs range from $800 to $10,000 depending on complexity. Most clients recoup the investment within 3 months through reduced support costs and faster releases.

What is included in the report?

You receive a detailed bug report with severity classification, reproduction steps, logs, screenshots, and code-level fix recommendations. We also provide a test coverage matrix and retest results.

Trust our experience

We have been delivering QA services for 5+ years, with certifications in Bitrix and Playwright. Our team has contributed to official Bitrix documentation and open-source testing tools. Guaranteed satisfaction or your money back.

More Information

Duplicate Products on Page 3: A Bug That Goes to Production

A real case: an online store with pagination through bitrix:catalog.section duplicates products on page three after every second visit. Cache clearing helps for a day, then the duplicates return. Root cause: a custom sort handler collides with PAGEN_1, and under a specific filter combination CIBlockElement::GetList returns identical IDs. Code review missed it; only testing caught it. We build QA for 1C-Bitrix projects that catches such bugs before they hit production: manual functional, automated E2E, load, and acceptance testing. With over a decade of Bitrix experience, we have a library of typical pitfalls and test scenarios that prevent these issues from the start.

How Does a Standard Bitrix Project Break Without Dedicated Testing?

1C-Bitrix is not a landing page. Behind the frontend lie dozens of modules, external integrations, and non‑obvious dependencies. A discount change in sale.discount breaks a promo code in sale.basket.discount — the discount module is one of the most fragile in the platform. Interchange with 1C via catalog.import.1c or REST fails when property mapping is off, resulting in products without price or stock. Core updates — bitrix:main updated, a custom component uses the deprecated CModule::IncludeModule. Without regression testing, every deployment is Russian roulette. Cross‑browser: sale.order.ajax renders differently in Safari and Chrome; the “Place Order” button can move off‑screen on an iPhone. These are not edge cases — they are daily realities for Bitrix teams.

What Does Functional Testing Cover?

We check every business scenario — not just “works or doesn’t work”, but all boundary cases.

Catalog (catalog.section, catalog.element)

• Smart filter catalog.smart.filter: all property combinations, reset, result counting. Filters by SKUs break most often.
• Sorting + pagination — the duplicate bug described above.
• Comparison via catalog.compare.list — add, remove, display differences.
• Quick view — modal window, cart from modal.

Cart and Order (sale.basket.basket, sale.order.ajax)

• Adding from catalog, product page, quick order.
• Discounts: by quantity, by amount, by coupon, cumulative. Discount intersection — at least eight test combinations.
• Delivery calculation: handlers sale.delivery.services, cost, time, pickup points on map.
• Payment: sale.paysystem — processing, handling declines, refunds.
• Order placement: email via main.mail.event, CRM recording, transmission to 1C via sale.export.1c.

Personal Account (sale.personal.section)

• Registration, authorization, password recovery — including Cyrillic email edge cases.
• Order history, repeat order.
• Subscriptions, bonus program.

Forms and Search

• form.result.new / iblock.element.add.form — submission, validation, file fields.
• search.page — relevance, morphology, typo handling via search.title.

Why Is Regression Testing Critical for Bitrix?

After every deployment we verify that nothing previously working is broken.

• Smoke tests — main page loads, catalog shows products, order completes. 5 minutes, run after every deploy. If smoke fails — roll back immediately.
• Regression suite — 40–80 test cases covering main scenarios before every release.
• Visual testing — screenshot comparison (Percy or Playwright). A button shifted 20px, font changed after update — test shows the diff.
• Module checklists — structured lists for sale, catalog, iblock, search. Each module has its own checklist.

What Happens During Load Testing?

The question is not “will the site handle it” but at how many concurrent users catalog.section starts returning 500 errors.

Tools:

• k6 — JavaScript scripting.
• Apache JMeter — classic, for complex scenarios with cookie authorization.
• Yandex.Tank — real‑time visualization, integration with Overload.

Output: peak RPS, response times by percentiles p50/p95/p99, bottlenecks (CPU, RAM, MySQL slow queries on b_iblock_element, file cache). Recommendations: which index to add, which query to rewrite with D7 ORM, where to enable composite cache.

What Deliverables Do You Receive After Testing?

• Test plan with scope, priorities, and quality criteria.
• Test case suite — functional, regression, load.
• Defect report in a tracker (Jira/YouTrack) with severity classification.
• Auto tests (Playwright/Cypress) — basic smoke suite for CI/CD.
• Load testing protocol with graphs and recommendations.
• Acceptance certificate after UAT — confirming readiness for launch.

After delivery, we provide free consultation for a month — answering questions on test improvements and process adaptation. Contact us to receive a full package of documents and auto tests.

Cross‑Browser Testing

We test where buyers actually are. Statistics from your Metrica are more important than general market data.

Minimum set:

• Chrome (last 2 versions) — main traffic.
• Safari on iOS — critical for mobile checkout, sale.order.ajax often behaves unpredictably.
• Yandex.Browser — significant share in Russia, Chromium‑based but with extension quirks.
• Samsung Internet — mobile Android, often forgotten.

Devices:

• Desktop: 1920×1080, 1366×768.
• iPhone: 375×812, 390×844 — checkout must be verified.
• Android: 360×800, 412×915.

Tools: BrowserStack for real devices, Playwright for automation on Chromium/Firefox/WebKit.

Automation

Playwright — primary choice for E2E on Bitrix:

• Cross‑browser: Chromium, Firefox, WebKit.
• Parallel execution, automatic waits.
• Works well with dynamic forms sale.order.ajax.
• Supports mobile viewports and geolocation.

Cypress:

• Runs in browser — more stable for SPA‑like interfaces.
• Excellent visual runner for debugging.
• Limitation: only Chromium‑based browsers.

PHPUnit for custom code:

• Unit tests for custom Bitrix components and modules.
• Tests business logic without frontend dependency.
• Integration with CI/CD — GitLab CI, GitHub Actions.

UAT – Acceptance Testing

Final check with the client on a staging environment with real data:

• Jointly compile a list of critical scenarios — 15–20 key customer paths, not 200 test cases.
• Staging with a copy of the production database (anonymized personal data).
• Quick bug tracking — Jira/YouTrack, prioritization by severity.
• Acceptance protocol — document with results, signatures, and launch readiness.

Order UAT support and we guarantee a release without surprises.

QA Process – Integrated, Not Tacked On

1. Requirements analysis — QA participates in task discussions, catches ambiguities. “Does the discount apply to the product or the order?” — such a question upfront saves two days of debugging.
2. Test cases before development — scenarios ready before the first line of code.
3. Code review — checks for typical Bitrix mistakes: uncleared component cache, direct SQL queries instead of ORM, missing $USER‑>IsAuthorized() check.
4. Functional → regression → deploy.
5. Post‑release monitoring — errors in bitrix/error.log, metrics in Metrica, alerts for 500 errors.

We have been working with Bitrix for over 10 years and have tested more than 300 projects of various scales — from small online stores to corporate portals with 1C and Bitrix24 integration.

Timelines

Testing cost is calculated individually for your project. Get a free consultation — we will assess the scope within one business day and provide a preliminary estimate and test plan. Contact us to discuss your project and schedule a call.