Linux iad1-shared-b7-18 6.6.49-grsec-jammy+ #10 SMP Thu Sep 12 23:23:08 UTC 2024 x86_64
Apache
: 67.205.6.31 | : 216.73.216.47
Cant Read [ /etc/named.conf ]
8.2.29
fernandoquevedo
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
README
+ Create Folder
+ Create File
/
usr /
local /
wp /
vendor /
wp-cli /
wp-cli-tests /
features /
[ HOME SHELL ]
Name
Size
Permission
Action
http-mocking.feature
6.94
KB
-rw-r--r--
steps.feature
2.3
KB
-rw-r--r--
testing.feature
1.38
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : testing.feature
Feature: Test that WP-CLI loads. Scenario: WP-CLI loads for your tests Given a WP install When I run `wp eval 'echo "Hello world.";'` Then STDOUT should contain: """ Hello world. """ Scenario: WP Cron is disabled by default Given a WP install And a test_cron.php file: """ <?php $cron_disabled = defined( "DISABLE_WP_CRON" ) ? DISABLE_WP_CRON : false; echo 'DISABLE_WP_CRON is: ' . ( $cron_disabled ? 'true' : 'false' ); """ When I run `wp eval-file test_cron.php` Then STDOUT should be: """ DISABLE_WP_CRON is: true """ @require-sqlite Scenario: Uses SQLite Given a WP install When I run `wp eval 'echo DB_ENGINE;'` Then STDOUT should contain: """ sqlite """ @require-mysql Scenario: Uses MySQL Given a WP install When I run `wp eval 'var_export( defined("DB_ENGINE") );'` Then STDOUT should be: """ false """ @require-sqlite Scenario: Custom wp-content directory Given a WP install And a custom wp-content directory When I run `wp eval 'echo DB_ENGINE;'` Then STDOUT should contain: """ sqlite """ @require-sqlite Scenario: Composer installation Given a WP install with Composer When I run `wp eval 'echo DB_ENGINE;'` Then STDOUT should contain: """ sqlite """
Close