cPanel 110 PHP Version Selector defaulting to 8.3: how should integration tests handle the change?

Answer the question directly

Pin the PHP version for each test account at provision time using the WHM API php_set_version. If you cannot change versions, discover the effective version after account creation with the uAPI call PHPVersion get_user_php_version and adapt test expectations accordingly. Changing the server‑wide default is possible but requires root/reseller privileges and affects all accounts, so it is only advisable in isolated test environments.

Likely explanation vs. confirmed facts

Confirmed: cPanel 110 sets PHP 8.3 as the default for newly created accounts; existing accounts keep their previously selected version. The WHM API php_set_version can set a specific version per account, and the uAPI PHPVersion get_user_php_version returns the active version for a given user.

Likely explanation: Tests that assumed a static default now encounter a split behavior because fresh accounts default to 8.3 while upgraded accounts retain older versions. Without explicit versioning, test results become nondeterministic.

Steps to make integration tests deterministic

1. Provision the test account via your usual automation (API, CLI, or UI).
2. Immediately call the WHM API php_set_version for that account, specifying a known version (e.g., 8.2) that your application supports.
3. Run the validation matrix against the account; the PHP runtime is now fixed regardless of the server‑wide default.
4. If you lack permission to call php_set_version, after provisioning retrieve the active version with uapi --user=<account> PHPVersion get_user_php_version and adjust assertions to match the returned value.

Covering both upgrade paths in one suite

Maintain two fixtures:

• Fresh account fixture – creates a new account on the cPanel 110 server; expects the version to equal the server‑wide default (8.3) unless you explicitly set it.
• Pre‑upgrade account fixture** – clones a snapshot of an account taken before the cPanel 110 upgrade (or creates an account and then manually sets its version to the prior default). This fixture validates the "existing account keeps its version" path.

Run the same test suite against each fixture; the only difference is the expected PHP version, which you can obtain from the fixture metadata or via the discovery API call.

When a missing detail changes the recommendation

Do you have root or reseller privileges on the test cPanel server? If you do not have such privileges, you cannot change the server‑wide default with php_set_vhost_versions, and the only reliable options are to pin per‑account versions (if allowed) or to discover and adapt. If you do have privileged access, you may set a server‑wide default for the reseller owning the test accounts to keep fixtures stable across upgrades, but remember that this change affects every account under that reseller.