Thanks for all the valuable feedback! I will definitely put some more love into the documentation to make some things easier to understand.
You figured out most of the stuff yourself. Here’s a small recap and some thoughts on your comments
- We simply use a spec combined with
defeffectto define effects. In the body of thedefeffectfunction we define our default (production) behavior - In our code base, we have several occasions where we use
defeffectto make side-effects explicit but don’t use it for testing. Making side-effects explicit and call them what they are is one purpose of the library - Yes it is a mocking library but focused on the semantics, that we have side-effects. We don’t talk about config, about how to mock, about technicals. Just side-effects.
- Generic automatic tagging is impossible. So … we don’t.
- We can test more code async than in e.g. mox, without allowance (see this test-case), but not all. The processes under test need the test-process to be an ancestor. E.g. in our code-base we need to set async to
falseif we test oban jobs, since they are located in the supervision tree of the oban application.
Again thanks for your feedback, that helps us to improve the library.
(see 