Releases: lucatume/wp-browser
Releases · lucatume/wp-browser
2.2.21
Added
- the
tad\WPBrowser\slug
function to create the slug version of a string
- the
tad\WPBrowser\buildCommandLine
function to generate a Symfony Process compatible command line (array format) from a string one
- the
tad\WPBrowser\renderString
function to render a string in the Handlebars format from data
- the
WPCLI::cliToString
method to get a wp-cli command output as string, fixes #297
Changed
- removed the
bacon/bacon-string-utils
dependency
- added support for custom extra arguments to the
WPCLI
module, see documentation, fixes #295
- replaced the
xamin/handlebars.php
dependency with the zordius/lightncandy
one
Fixed
- lazy evaluation of the WordPress path in
WPCLI
module, fixes #294
- correct evaluation of command exit status in
WPCLI
module, fixes #296
2.2.20
Fixed
- ignore foreign key checks when dropping tables in isolated install (thanks @TimothyBJacobs)
2.2.19
Fixed
- enhancements to the build scripts (thanks @karser)
- avoid redefining constants during
WPLoader
module bootstrap
2.2.18
Fixed
WPLoader
module: load WordPress on SUITE_INIT
when only loading (#283)
2.2.17
Fixed
- eager instantiation of WordPress factories causing warnings (#281)
2.2.16
Added
- expose a
tad\WPBrowser\Module\WPLoader\FactoryStore
instance on the $tester
property when loading the WPLoader
module with loadOnly: false
.
Fixed
- add explicit override of the
$tester
property when scaffolding the WPTestCase
class (thanks @Luc45)
2.2.15
Fixed
- call
Codeception\Test\Unit
setup methods in WPTestCase
to provide Codeception Unit testing facilities in "WordPress unit" test cases [#261 #262 ]
2.2.14
Fixed
- remove left-over
%WP_URL%
from generated configuration files when runnin codecept init wpbrowser
and replace it with %TEST_SITE_WP_URL%
(thanks @HendrikRoehm)
2.2.13
Fixed
- when the
WPLoader
module is set to loadOnly
mode and used in conjunction with a *Db
module delay its load after all other modules ran their _beforeSuite
action; this tackles an issue only partially resolved in 2.2.8
(thanks @Luc45)
2.2.12
Fixed
- make sure Cron is disabled while
WPLoader
module is installing WordPress in isolation (default mode)