tad\WPBrowser\Extension\Symlinkerextension provides an automation to have the Codeception root directory symbolically linked in a WordPress local installation.
mode- can be
themeand indicates whether the current Codeception root folder being symlinked is a plugin or a theme one
destination- the absolute path to the WordPress local installation plugins or themes folder; to take the never ending variety of possible setups into account the extension will make no checks on the nature of the destination: could be any folder.
rootFolder- optional absolute path to the WordPress plugin or theme to be symlinked root folder; will default to the Codeception root folder
tad\WPBrowser\Extension\Copierextension provides an automation to have specific files and folders copied to specified destination files and folders before the suites run.
mu-plugin.phpfile should be copied to the
mu-pluginsfolder must be there already.
acceptance.suite.ymlfile might be configured to support
codeception.ymlfile specifying a
destinationfor each supported environment will tell the extension to symbolically link the plugin or theme file to different locations according to the current environment:
defaultdestination can be specified to override this behaviour.
multisitedestination will be used.
rootFolderparameter too can be set to be environment-aware and it will follow the same logic as the destination:
4.0, the internal API (really a collection of low-level hacks on my part) that allowed
wp-browserto dispatch, and listen for, events in the modules has been removed.
test.before), then you will need to use this extension.
suitesparameter that allows specifying the suites the extension should apply to. If the
suitesparameter is not specified, then the extension will apply to all suites.