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
{{ message }}
This repository has been archived by the owner on Feb 24, 2024. It is now read-only.
Lately I've been finding myself using test suites more and more in my applications. I'm wondering if this is something that we should add to Buffalo. While this proposal talks about ActionSuite that would be used for testing actions, a similar one, ModelSuite, would be created for testing models.
My typical ActionSuite usually looks something like this:
I like this idea, i understand the trade-offs buffalo would be making by introducing this but IMHO the wins are larger and will make testing easier/faster while increasing productivity.
Thanks @markbates for sharing this proposal, hoping to see this getting into buffalo soon and willing to help as possible.
Lately I've been finding myself using test suites more and more in my applications. I'm wondering if this is something that we should add to Buffalo. While this proposal talks about
ActionSuite
that would be used for testing actions, a similar one,ModelSuite
, would be created for testing models.My typical
ActionSuite
usually looks something like this:Then in my
actions/actions_test.go
file I would create aTest
function that looks something like this:Which means my tests now look like this:
I find this really nice and clean, and means I can add nice setup/teardown to my tests.
So the question is should this be included in Buffalo or should I release this as a separate package that people can use if they desire?
Included in Buffalo Pros/Cons:
Pros
testify
is already being depended on by Buffalo, so there's no extra dependencyCons
Separate Package Pros/Cons:
Pros
Cons
I'm looking for thoughts/opinions on this.
The text was updated successfully, but these errors were encountered: