You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tests/Tokenizer: make failure messages more descriptive
Most Tokenizer tests first assert that the token `'code'` is correct and after that, that the token `'type'` is correct.
When the first assertion fails, an error message like this will be displayed:
`Failed asserting that 357 is identical to 313.`
That's because the PHP native token constants are integers. And even if someone would memorize all token constant integers, the integer values are different depending on the PHP version being used. All in all, that makes error messages like the above hard to decipher.
To mitigate this, a number of the Tokenizer tests already used the `$msg` parameter for the `assertSame()` call.
This commit adds this `$msg` parameter to more assertions to make the failure messages actually useful.
Includes introducing an interim `$tokenArray` variable in a lot of these tests to keep the line length in check.
0 commit comments