It is generally recommended to explicitly declare the visibility for methods.
Adding explicit visibility (private, protected, or public) is generally
recommend to communicate to other developers how, and from where this method
is intended to be used.
It is generally recommended to explicitly declare the visibility for methods.
Adding explicit visibility (private, protected, or public) is generally
recommend to communicate to other developers how, and from where this method
is intended to be used.
Loading history...
20
{
21
22
$this->taskExec('mysql -e "CREATE DATABASE IF NOT EXISTS test_db"')->run();
23
$this->taskExec('mysql -e "GRANT ALL ON test_db.* to \'root\'@\'%\'"')->run();
It is generally recommended to explicitly declare the visibility for methods.
Adding explicit visibility (private, protected, or public) is generally
recommend to communicate to other developers how, and from where this method
is intended to be used.
Loading history...
34
{
35
$this->taskPhpUnit('vendor/bin/phpunit')
36
->configFile('tests/phpunit.xml.dist')
37
->envVars(array('WP_TESTS_DIR' => 'wp-tests'))
38
->run();
39
}
40
41
private function setTestConfig()
42
{
43
44
if (file_exists('wp-tests/wp-tests-config-sample.php')) {
You can fix this by adding a namespace to your class:
When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.