| Server IP : 51.254.39.36 / Your IP : 216.73.217.109 Web Server : Microsoft-IIS/10.0 System : Windows NT WIN-12GDIEC772I 10.0 build 20348 (Windows Server 2022) AMD64 User : IWPD_21(allbatf787) ( 0) PHP Version : 8.3.32 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : OFF | Perl : OFF | Python : OFF | Sudo : OFF | Pkexec : OFF Directory : C:/Inetpub/vhosts/allbat-sb.fr/httpdocs/wp-content/plugins/kadence-blocks/ |
Upload File : |
# This file will be consumed by both the CI and the tests. # Some environment variables might not apply to one but might apply to the other: modify with care. SLIC_PHP_VERSION=8.0 # What version of WordPress we want to install and test against. # This has to be compatible with the `wp core download` command, see https://developer.wordpress.org/cli/commands/core/download/. WP_VERSION=latest # This is where, in the context of the CI, we'll install and configure WordPress. # See `.travis.yml` for more information. WP_ROOT_FOLDER=/var/www/html # The WordPress installation will be served from the Docker container. # See `dev/docker/ci-compose.yml` for more information. WP_URL=http://wordpress.test WP_DOMAIN=wordpress.test WP_ADMIN_PATH=/wp-admin # The credentials that will be used to access the site in acceptance tests # in methods like `$I->loginAsAdmin();`. WP_ADMIN_USERNAME=admin WP_ADMIN_PASSWORD=password WP_DB_PORT=3306 # The databse is served from the Docker `db` container. # See `dev/docker/ci-compose.yml` for more information. WP_TABLE_PREFIX=wp_ WP_DB_HOST=db WP_DB_NAME=test WP_DB_USER=root WP_DB_PASSWORD=password # The test databse is served from the Docker `db` container. # See `dev/docker/ci-compose.yml` for more information. WP_TEST_DB_HOST=db WP_TEST_DB_NAME=test WP_TEST_DB_USER=root WP_TEST_DB_PASSWORD=password # We're using Selenium and Chrome for acceptance testing. # In CI context we're starting a Docker container to handle that. # See the `dev/docker/ci-compose.yml` file. CHROMEDRIVER_HOST=chrome CHROMEDRIVER_PORT=4444 # The URL of the WordPress installation from the point of view of the Chromedriver container. # Why not just use `wordpress`? While Chrome will accept an `http://wordpress` address WordPress # will not, we call the WordPress container with a seemingly looking legit URL and leverage the # lines that, in the `wp-config.php` file, will make it so that WordPress will use as its home # URL whatever URL we reach it with. # See the `dev/docker/wp-config.php` template for more information. WP_CHROMEDRIVER_URL=http://wordpress.test # To run the tests let's force the background-processing lib to run in synchronous (single PHP thread) mode. TRIBE_NO_ASYNC=1 # We're using Docker to run the tests. USING_CONTAINERS=1