We just added some minor features to Efx 0.2.10:

• We love to hotfix our code. Efx now allows to paste code directly into your production environment, if needed. Until now this wasn’t possible, because the hard dependency to Mix.env. We fixed that.
• We fell in love with property based testing, in our case StreamData. Since uncontrolled and slow side effects are a burden in property based testing, Efx is a obvious choice to bind and control them. However, since Efx works in a process scope and StreamData executes multiple tests in the very same process, binding for each test-case doesn’t work. To enable Efx for property based testing, we introduced with_clean_bindings, which can be used in the body of a propery based test to achieve case dependent bindings: EfxCase — Efx v1.0.1

Happy hotfixing, testing and coding!

We just released Efx 1.0.0

After some input from the community and minor bug fixes, we thought about our own usage patterns and slightly altered the binding-syntax in a backwards compatible way:

• Bindings are now done using functions captures, e.g. bind(&MyEffects.write/1, fn _ -> :ok end). Before, we had to name the module as a first argument and pass the function name as an atom as the second.
• Using function captures does not only provide hints for the compiler but also is enables auto completion support for most editors.
• Given that syntax we can now cover a very common use case that covers 90% of our tests: Returning a constant from bindings. We can now easily create bindings that return one value constantly: bind(&MyEffects.write/1, const: :ok).

Happy coding!

It is a mocking library, that doesn‘t need global binding for your test cases. So all mocking and preparation happens directly in your test code. No need for configs or anything else.

I started using it in my projects and it makes testing clearer and easier.

Kudos to @murrgelb