Testing and Validation

Testing and validation

This documentation is based on code review and limited local checks. It is not a certification of production readiness or a successful live NetSuite integration.

Evidence for the reviewed version

Check	Result on September 9, 2026
Repository	mage-os-lab/module-netsuite-connector, default branch main, commit fec65e2b67e18da3d9d3bf4c007d3c7fd5228537.
Scope	754 tracked files, including 668 PHP files and 19 XML files. Source, configuration, schema, UI, tests/fixtures, and package metadata were inventoried and reviewed by subsystem.
Composer manifest	composer validate --strict --no-check-publish passed.
PHP syntax	php -l passed for all 668 PHP files using PHP 8.5.9.
XML	All 19 XML files parsed successfully. This was XML well-formedness validation, not Magento XSD validation.
Focused behavior probes	Confirmed the multi-source shipment array/Record mismatch, the missing location-import method, the product constant-option value mismatch, and the exception for an unset discount provider using isolated PHP stubs and the real source classes.
Test source	37 unit-test files and 28 integration-test files ending in Test.php, plus supporting fixtures and test infrastructure.
Automated execution evidence	No GitHub Actions runs or repository workflow definitions were present at review time.
Publication	Packagist exposed dev-main at the reviewed source commit; no tagged release was present.

PHP syntax validation does not load Magento dependencies or prove DI compilation, database setup, test behavior, account permissions, or successful SOAP writes. The focused probes establish specific source contracts; they do not substitute for the full application.

Included tests and missing harness

Tests are grouped under each feature's Test/Unit and Test/Integration directories. Core includes NetSuite record-building and recorder/faker infrastructure, with serialized response fixtures under the test trees. Some older _files_ns helpers are designed to operate against NetSuite.

The repository does not contain a standalone dev/ test harness, PHPUnit configuration, installed dependencies, or a Magento application bootstrap. The old integration-test guide assumes a full Magento installation and paths that are not present in this standalone module checkout.

To run tests, install the module in a disposable compatible store, use the host application's test infrastructure, and configure a test suite that loads the module's test directories. Review fixture behavior first. Do not point fixture-recording or remote-data helpers at a production account. Record the store version, PHP version, installed dependency versions, module commit, command, and exact suite result.

The README lists Mage-OS 3.4.0 and Magento Open Source 2.4.8-p4. Those statements were not independently established by this review's syntax checks.

Sandbox acceptance sequence

1. Install and run database setup and DI compilation in a disposable host application. Confirm module status, Admin settings, ACLs, monitor rendering, and actual database schema.
2. Test credentials with the server-time request, then independently test the record searches, custom fields, files, and writes required by the enabled flows.
3. Import representative simple, configurable, kit bundle, assembly, non-inventory, and item-group products used by the business. Compare SKU, type, required attributes, website/store assignment, prices, tiers, links, visibility, and stock behavior.
4. Test image additions, removals, identical filenames with changed content, missing files, and a product with an empty remote image list.
5. Test customer matching by linked ID, external ID, and email; guest order resolution; address replacement; multi-website collisions; and imported-customer password setup.
6. Export an order with real project payment/shipping mappings, custom fields, tax, discounts, configurable/bundle items, and partial quantities. Compare all transaction totals in both systems.
7. Import the supported order changes, cash sale, shipped fulfillment with tracking, and refund record. Verify linked entities, quantities, totals, notifications, and payment effects separately.
8. Exercise saved-search stock imports including zero quantities, omitted rows, repeated rows, unknown IDs, and source mappings. Compare source quantity and salable quantity through order placement, cancellation, export failure, fulfillment, and retry.
9. Test network errors, expired searches, interrupted workers, malformed data, repeated records, uncertain remote writes, Run Again, and monitor retention. Verify that operators can reconcile a failure without duplicating transactions.
10. Verify the actual scheduler, queue progress, stock cadence, log rotation, independent alerts, and backup/restore procedure before production acceptance.

The known multi-location and queue defects remain blockers for the corresponding acceptance claims until corrected and retested. Test assets in the tree are evidence of intended scenarios, not evidence that this exact package passed them.

Sources: manifest, README, Core test infrastructure, queue integration tests, Code map, Known limitations.