We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It's time to start testing our standards. There are some precedents we can look to in https://github.com/squizlabs/PHP_CodeSniffer/tree/master/tests and https://github.com/slevomat/coding-standard/tree/master/tests. They take slightly different approaches; I think both will be informative. Alternatively, PHP itself has a very nice PHPT test file format that encapsulated very granular assertions all in one file (with the ability to use external fixtures still). (Example. Observe the --FILE-- and --EXPECTF-- sections, in particular.) I wouldn't mind adding either of these approaches to my toolkit.
--FILE--
--EXPECTF--
test
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It's time to start testing our standards. There are some precedents we can look to in https://github.com/squizlabs/PHP_CodeSniffer/tree/master/tests and https://github.com/slevomat/coding-standard/tree/master/tests. They take slightly different approaches; I think both will be informative. Alternatively, PHP itself has a very nice PHPT test file format that encapsulated very granular assertions all in one file (with the ability to use external fixtures still). (Example. Observe the
--FILE--
and--EXPECTF--
sections, in particular.) I wouldn't mind adding either of these approaches to my toolkit.test
Composer custom script.The text was updated successfully, but these errors were encountered: