New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Built-in assertion and mock type definitions #3708
Built-in assertion and mock type definitions #3708
Commits on Jun 5, 2019
-
Split assertion type-check tests into isolated test scenarios
Each file verifies that the type can be correctly inferred
-
Added
psalm.xml
configuration file to check the happy-path static s……cenarios This is a temporary file location, since the project has its own conventions
-
-
PropertyNotSetInConstructor
cannot be avoided inTestCase
child c……lasses Suppressing the error here.
-
Disabling type declarations for trait mocking
TestCase
methodsTraits are no real types, therefore we cannot support their usage in templated types.
-
Corrected
Assert::assertIs(Not)Scalar()
type assertionsIncorrect docblock format was used, and incorrect return type was used in the test scenario.
-
Using objects/integers to verify
assert(Not)Empty
type assertionsThis is a workaround to not require vimeo/psalm#1743 to be fixed first
-
Failures should be allowed on PHP nightly
`master` was being used instead, but no such version is present in the build matrix.
-
Excluded static-analysis directory from CS-fixer paths
Annotations such as `@return numeric` are not recognized by this tooling, so for now this test suite is off-limits for `php-cs-fixer`.