-
Notifications
You must be signed in to change notification settings - Fork 177
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
Rework testing fixtures #74
Comments
The current fixtures package should go away, and knowledge of how to create fixtures for given models (structs) should reside next to the structs themselves within the test code for that package. E.g. in the |
@portertech @palourde @amdprophet -- I would love some feedback on this approach. If you'd like, I can concretize this in a PR this week so you can see exactly what I'm talking about. |
Toss it into types! 👍 |
We need to migrate older test code to use this method of fixtures. |
Fixed with #97 |
I want us to move to an Interface + Mock methodology for unit testing. So instead of having an in-memory fixture store that's incapable of easily simulating all interactions with a Store (i.e. simulating error cases is brittle and/or non-trivial), I'd like us to move back to the mock store that was there before + testify.mock behavior simulation in faked methods per test. (We can develop some reusable faked methods if this ends up being super copypasta).
The key being that the mock should simulate behavio
The text was updated successfully, but these errors were encountered: