It seems that when we use multisite configuration the integration tests load site from test.local/php7_multisite
but acceptance tests run on test.local
So let's activate correct theme on both
[MAILPOET-5925]
After we updated the oldest supported WP and PHP versions, we don't need this theme anymore.
When I checked recent builds, I notice we are getting:
Error: The 'twentynineteen' theme could not be found.
So it already works for some time without the theme being activated.
[MAILPOET-5925]
There is an integration test that is intentionally failing in case
we changed the theme we used for the test.
This commit ensures we activate correct theme also for multisite.
[MAILPOET-5741]
This is replacement for custom wait scripts and also should ensure
that DB is ready before starting the wordpress serive container,
which was missing the check.
[MAILPOET-4851]
When mounted the plugin was mounted directly to the plugin folder get_plugins() function
ignored it. We had a similar issue in the past when we were using a softlink.
Copying the plugin is a workaround that fixes the issue.
[MAILPOET-4662]
We need to delete those files before we activate the plugin.
When we do it after the activation there might already be a background request and we may delete those files
during the request.
[MAILPOET-4662]
We need to provide correct --url parameter to WP CLI commands so that
in multisite environment the correct site is affected.
Otherwise the plugins might not be activated for site we run tests on.
[MAILPOET-4625]
In case $SKIP_PLUGINS is set to 1 we don't activate installed plugins so it makes no sense to install them as well.
In this commit we add also skipping the installation of the plugins.
[MAILPOET-4566]
We experienced issues with replacing constants in wp-config.php using regular expressions.
E.g. it may stop working when new WP release changes default contents of the wp-config.php
Using WP CLI seems to be more reliable way of doing it.
[MAILPOET-4511]
The wp-config properties were not set correctly because there reg exp
that was used in sed was no longer matching the default value.
This was causing e.g. that errors and warnings were not caught by the acceptnace tests.
[MAILPOET-4511]
The doctrine/annotation is not present in the production build.
This change makes the acceptance tests runtime closer the production environment.
[MAILPOET-4218]
