Documentation VIP Go Testing Jetpack on VIP Go

Testing Jetpack on VIP Go

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.

When Jetpack beta and release candidate versions are available, the WordPress.com VIP team will maintain a copy of the latest of these versions in the VIP Go MU plugins for you to test against. To load this version, define the VIP_JETPACK_ALT constant as true as follows:

define( 'VIP_JETPACK_ALT', 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( 'VIP_JETPACK_ALT', true );
}

If there is no beta or release candidate version of Jetpack available, the current release version of Jetpack will be loaded even if you have defined the VIP_JETPACK_ALT constant as true.

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