WP Browser bug squashed

September 12, 2014

Bug killing

I've fixed the bug preventing a clean bootstrap experience using the wpcept wpbootstrap command that comes with the WP Browser Codeception add-on and pushed the modification to the package master branch on GitHub.

Command argument modification

While I was there I've also decided to modify the command needed to bootstrap the tests in a test pyramid fashion to make things clearer: the wpcept command supplies methods specific to WordPress testing and adopting the aforementioned test organization is a personal taste unrelated to WordPress. As such I've replaced the command

wpcept wpbootstrap

with

wpcept bootstrap:pyramid

So now running the command

wpcept bootstrap

will bootstrap the test suites like

unit with Asserts and UnitHelper modules
functional with Filesystem, WPDb, WPLoader and FunctionalHelper modules
acceptance with WPBrowser, WPDb and AcceptanceHelper modules [](http://theaveragedev.local/wordpress/wp-content/uploads/2014/09/2014-09-12-at-15.03-2.png)

while using the command

wpcept bootstrap:pyramid

will bootstrap the test suites the "alternative" way:

unit with Asserts and UnitHelper modules
service with Filesystem, WPDb, WPLoader and ServiceHelper modules
ui with WPBrowser, WPDb and UIHelper modules [](http://theaveragedev.local/wordpress/wp-content/uploads/2014/09/2014-09-12-at-15.03.png) It's nothing more but a name change but I felt like it was needed.
The possibility to bootstrap suites the default Codeception way remains using the codecept command.