-
-
Notifications
You must be signed in to change notification settings - Fork 400
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
Testing refactor #658
Comments
@Daanra You already have permissions to maintain this package right? |
@nunomaduro I do have write permissions for this repository, if that's what you meant. I could take a stab at this refactor if nobody has any concrete plans for it yet. |
I'd like to use the |
I am also not happy with the current test suite. Feel free to make a pull request to improve this in the future. |
Description
Currently, the FeaturesTests that we use do not allow you to assert whether Larastan reports an error for a specific piece of code. Instead, we can only test whether Larastan reports no errors.
It would be if we could add functionality that allows us to assert that Larastan reports certain errors. In addition, it would be nice if we could change Larastan's config during a test such that we can, for example, test functionality that is disabled by default.
Created a separate issue because of this comment
The text was updated successfully, but these errors were encountered: