Documentation VIP Go Testing Jetpack on VIP Go

Testing Jetpack on VIP Go

Overview #

Automattic tests Jetpack releases against a diverse range of environments and sites, to assess performance with various levels of data and traffic. There is also an automated Jetpack test suite, run on Travis, which you can follow. As the Jetpack code is a significant proportion of your VIP Go site, we recommend you test your particular functionality against betas and release candidates of Jetpack as they become available. In advance of a Jetpack release, the WordPress.com VIP team will post in the Lobby to keep you informed, we’ll post to our @wpvipstatus when Jetpack or WordPress are updated on VIP Go.

This document describes how to switch your VIP Go site(s) and development environment to use the current beta or release candidate version of Jetpack. You may wish to read about VIP Go sites and environments.

↑ Top ↑

Step 1: Add the version of Jetpack to be tested #

Commit the version of Jetpack you wish to test into your VIP Go site GitHub repository, add it as a plugin inside the `plugins` directory.

↑ Top ↑

Step 2: Load the “local” version of Jetpack #

By default, VIP Go will load Jetpack from the MU plugins directory. Using the `WPCOM_VIP_JETPACK_LOCAL` constant, you can instruct VIP Go to load Jetpack from the `plugins` folder.

define( 'WPCOM_VIP_JETPACK_LOCAL', true );

If you want to avoid testing on your production site, for example during the beta period (you may choose to run the release candidate on your production site):

$disallowed_jetpack_test_envs = array(
    'production',
);
if ( ! in_array( VIP_GO_ENV, $disallowed_jetpack_test_envs, true ) ) {
    define( 'WPCOM_VIP_JETPACK_LOCAL', true );
}

Note that the previous method of testing Jetpack using the `VIP_JETPACK_ALT` is discontinued, and this constant will have no effect.

Documentation is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.