Linux ip-172-26-2-223 5.4.0-1018-aws #18-Ubuntu SMP Wed Jun 24 01:15:00 UTC 2020 x86_64
Apache
: 172.26.2.223 | : 3.16.188.113
Cant Read [ /etc/named.conf ]
8.1.13
www
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
BLACK DEFEND!
README
+ Create Folder
+ Create File
/
usr /
share /
cmake-3.16 /
Help /
prop_test /
[ HOME SHELL ]
Name
Size
Permission
Action
ATTACHED_FILES.rst
206
B
-rw-r--r--
ATTACHED_FILES_ON_FAIL.rst
218
B
-rw-r--r--
COST.rst
621
B
-rw-r--r--
DEPENDS.rst
467
B
-rw-r--r--
DISABLED.rst
712
B
-rw-r--r--
ENVIRONMENT.rst
323
B
-rw-r--r--
FAIL_REGULAR_EXPRESSION.rst
406
B
-rw-r--r--
FIXTURES_CLEANUP.rst
1.83
KB
-rw-r--r--
FIXTURES_REQUIRED.rst
4.8
KB
-rw-r--r--
FIXTURES_SETUP.rst
1.89
KB
-rw-r--r--
LABELS.rst
117
B
-rw-r--r--
MEASUREMENT.rst
286
B
-rw-r--r--
PASS_REGULAR_EXPRESSION.rst
483
B
-rw-r--r--
PROCESSORS.rst
679
B
-rw-r--r--
PROCESSOR_AFFINITY.rst
643
B
-rw-r--r--
REQUIRED_FILES.rst
155
B
-rw-r--r--
RESOURCE_GROUPS.rst
3.45
KB
-rw-r--r--
RESOURCE_LOCK.rst
805
B
-rw-r--r--
RUN_SERIAL.rst
233
B
-rw-r--r--
SKIP_REGULAR_EXPRESSION.rst
490
B
-rw-r--r--
SKIP_RETURN_CODE.rst
442
B
-rw-r--r--
TIMEOUT.rst
318
B
-rw-r--r--
TIMEOUT_AFTER_MATCH.rst
1.39
KB
-rw-r--r--
WILL_FAIL.rst
184
B
-rw-r--r--
WORKING_DIRECTORY.rst
328
B
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : FIXTURES_SETUP.rst
FIXTURES_SETUP -------------- Specifies a list of fixtures for which the test is to be treated as a setup test. These fixture names are distinct from test case names and are not required to have any similarity to the names of tests associated with them. Fixture setup tests are ordinary tests with all of the usual test functionality. Setting the ``FIXTURES_SETUP`` property for a test has two primary effects: - CTest will ensure the test executes before any other test which lists the fixture name(s) in its :prop_test:`FIXTURES_REQUIRED` property. - If CTest is asked to run only a subset of tests (e.g. using regular expressions or the ``--rerun-failed`` option) and the setup test is not in the set of tests to run, it will automatically be added if any tests in the set require any fixture listed in ``FIXTURES_SETUP``. A setup test can have multiple fixtures listed in its ``FIXTURES_SETUP`` property. It will execute only once for the whole CTest run, not once for each fixture. A fixture can also have more than one setup test defined. If there are multiple setup tests for a fixture, projects can control their order with the usual :prop_test:`DEPENDS` test property if necessary. A setup test is allowed to require other fixtures, but not any fixture listed in its ``FIXTURES_SETUP`` property. For example: .. code-block:: cmake # Ok: dependent fixture is different to setup set_tests_properties(setupFoo PROPERTIES FIXTURES_SETUP Foo FIXTURES_REQUIRED Bar ) # Error: cannot require same fixture as setup set_tests_properties(setupFoo PROPERTIES FIXTURES_SETUP Foo FIXTURES_REQUIRED Foo ) If any of a fixture's setup tests fail, none of the tests listing that fixture in its :prop_test:`FIXTURES_REQUIRED` property will be run. Cleanup tests will, however, still be executed. See :prop_test:`FIXTURES_REQUIRED` for a more complete discussion of how to use test fixtures.
Close