PDOException when using WPDb and WPLoader in different suites about wp-browser HOT 11 CLOSED

The WPLoader module will work on the database installing WordPress and destroying it in the process.
The WPDB module you are using with the populate and cleanup parameters set to true.
What's happening is that one of the two modules will not find the db tables it's looking for.
WPLoader is not built on top of PHPUnit: it's a module taking care of loading WordPress the same way the tests provided by the core team do.

Could you post the suites config files?

from wp-browser.

What I meant is that the WP core tests are based on PHPUnit, bad wording sorry...

I am aware if issues between WPDb and WPLoader but in my case, I am not using both modules in the same suite along with Cest tests. Everything works fine with both modules when using the Test format however, like I do in unit & acceptance tests.

My suite config files are empty except for enabling the modules that you can see in the outputs above.

from wp-browser.

Ok, you are using the same database for both modules. Any databes WPLoader uses should be used for WPLoader alone.

from wp-browser.

Haaa I see. Is there a way to have access to the WP codebase/functions without using WPLoader. I'm using it only to have access to functions but I rather load a preset DB for my tests.

from wp-browser.

Why does it only occur with Cest tests???

from wp-browser.

Why does it only occur with Cest tests???

That might be due to the timing test run. The order is relevant.

Haaa I see. Is there a way to have access to the WP codebase/functions without using WPLoader. I'm using it only to have access to functions but I rather load a preset DB for my tests.

No, WPLoader will walk the same path as the core suite and require a db connection and the rather destructive approach.
What you can do is bootstrap a wp instance including the wp-load.php file. Just know that's exactly how WPLoader began.

from wp-browser.

I might do just that and create a PR
A new module that integrates the changes from the closed PR would fit well in this scenario.

from wp-browser.

You are more than welcome to do it, just keep contexts separated: e.g. a PR to add a test case method should not also contain a new Codeception Module

from wp-browser.

I'll read a bit more on the codeception framework along the way

from wp-browser.

This could probably help you: #32

Closing.

from wp-browser.

An update on this: I've added the WPBootstrapper module, might have a look at that and see how it helps; it's a first version though so anything missing just open an issue and label it "enhancement".

from wp-browser.