Closed justlevine closed 1 year ago
Hi @justlevine,
thanks for reporting an issue and providing debug information. I'm currently away from office and will come back in a couple weeks to lo into this and fix it.
@justlevine looking at the suite configuration file, you're using the WPDb
module together with the WPLoader
module.
The WPLoader
module is not in loadOnly: true
mode, though, see the documentation.
This means both the WPDb
module and the WPLoader
module will try to manage the database initial state.
If your purpose is to have WordPress and plugins functions available in the context of end-to-end tests, then:
WPDb
module to populate the databaseWPLoader
module to only load WordPress from the state populated by the WPDb
module.
Environment OS: Ubuntu 22.04.2 (GitHub runner) PHP version: 8.1 Installed Codeception version: 4.2.2 Installed wp-browser version: 3.1.9 WordPress version: 5.9-6.1 Local development environment: WSL2 + devilbox (ubuntu 20.0.4 php 8.1.13) WordPress structure and management: default
Did you use the
codecept init wpbrowser
command? yesDid you take a look at Codeception and wp-browser documentation? yes
Codeception configuration file
Suite configuration file If you're encountering an issue with a specific suite, please provide its configuration file.
Describe the issue you're encountering When running Codeception + WPBrowser as part of my ci, Codeception fails initialization due to PHP deprecation notices caused by the plugins I'm testing against.
When I run the failing acceptance test locally, the deprecation notices get printed to the console, but the tests complete as expected.
Output GH Action report
To Reproduce As noted, the issue the issue is happening in
harness-software/wp-graphql-gravity-forms
repo and not locally. I am happy to share the GH tokens necessary for the CI to work on a fork.Screenshots This is the output when running locally. Note it passes successfully.
Additional context The source of the error seems to be from #556