-
Notifications
You must be signed in to change notification settings - Fork 0
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
Tests #279
Comments
I think a good first step would actually be testing all the helper methods in The Helpers are all pure functions so are easy to test We can hook the models up to a dummy database (created before first test, dropped after last test) and fill with dummy data so we know what the queries should be returning |
Seems fair enough to me |
Seeing as I've broken everything and touched e v e r y s i n g l e f i l e for this change I'm working on, I'm seeing the importance of these tests more and more >.< I'm going to try and put a list of every action possible through the system here so that we can build tests based off them DB/System stuff
"Core" stuff
Config
Users
Membership
Organisation
Events
Bulk Emailer
|
We should probably add some form of automated testing now that we have an action runner.
I think running them before each commit is too restrictive and it's the purpose of pull requests to ensure that only working code makes it live - so I think passing tests should be a prerequisite of merging PRs.
This issue is a discussion/suggestion ticket as this issue is so large - any agreed on tests should be done in separate issues!
The text was updated successfully, but these errors were encountered: