Releases: lucatume/wp-browser
Releases · lucatume/wp-browser
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)
2.2.11
Added
- support for
timeout
parameter in WPCLI module configuration
2.2.8
Changed
- updated requirement of
codeception/codeception
to include version 3.0
- updated
WPTestCase
to handle PHPUnit version 8.0+
compatibility
- internalized the classes and functions provided by the
lucatume/wp-browser-commons
package
Fixed
- initialize the WPLoader module after all other modules initialized when
loadOnly
is true
to avoid WordPress exiting due to a non-initialized database fixture