-
-
Notifications
You must be signed in to change notification settings - Fork 71
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
Ensure that test has been really run #32
Comments
Missing Calling assertions seems like good idea. |
Having it runned by |
That can be done using http://php.net/manual/en/configuration.file.per-user.php, by I've never tried it. |
Why so complicated? |
Missing |
@dg Yop. If you think that checking ordinary tests (not TestCases) is not need it, close it please. Personaly I would check ordinary tests too. |
The only one case which is not checked is when you forget to call |
Yes. |
Sometimes can happend that none assertion is done in a test file, e.g. accidental die() before first assertion or just:
... test seems to be passing.
First idea is to count Assert::method() calls, check it in the shutdown function and fail or skip the test. The plus can be nothing-saying statistics :)
The text was updated successfully, but these errors were encountered: