If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
28
$seeder->/** @scrutinizer ignore-call */
29
run();
This check looks for calls to methods that do not seem to exist on a given type.
It looks for the method on the type itself as well as in inherited classes or
implemented interfaces.
This is most likely a typographical error or the method has been renamed.
Loading history...
29
}
30
31
// Seeder class string to be used in Artisan command
The method seed() does not exist on Sfneal\Testing\Utils\Traits\WithMemoryDbConnection. Did you maybe mean seeders()?
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
33
$this->/** @scrutinizer ignore-call */
34
seed($seeder);
This check looks for calls to methods that do not seem to exist on a given type.
It looks for the method on the type itself as well as in inherited classes or
implemented interfaces.
This is most likely a typographical error or the method has been renamed.
Loading history...
34
}
35
}
36
}
37
38
/**
39
* Performs assertions shared by all tests of a test case.
It seems like assertEquals() must be provided by classes using this trait. How about adding it as abstract method to this trait?
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
It seems like beforeApplicationDestroyed() must be provided by classes using this trait. How about adding it as abstract method to this trait?
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
57
$this->/** @scrutinizer ignore-call */
58
beforeApplicationDestroyed(function () {
Loading history...
58
DB::disconnect('testing');
59
});
60
61
parent::tearDown();
62
}
63
64
/**
65
* Retrieve an array of Seeders to be run within the `setUp()` method.
sfneal /
mock-models
Loading history...
This check looks for calls to methods that do not seem to exist on a given type. It looks for the method on the type itself as well as in inherited classes or implemented interfaces.
This is most likely a typographical error or the method has been renamed.