Problem with mockings about mecks_unit HOT 10 CLOSED

I guess missed that part ☹️
Thanks for explaining!

from mecks_unit.

Hey, there. I'll take a look at it this weekend

from mecks_unit.

Hey again, have given this any thought?

from mecks_unit.

I guess I have read your description incorrectly. The resulting behaviour is as expected. See also the README:

Please note that the defined mock modules only apply to the first mocked_test encountered. So they are isolated (despite of :meck having an unfortunate global effect) as MecksUnit takes care of it. Also, non-matching function heads within the mock module will result in invoking the original module function as well.

I had to change

assert Mocked.func2() === : returns_from_mocking

to

assert Mocked.func2() === :returns_from_module_a

to get the build succeeding (see: https://travis-ci.org/archan937/mecks_unit)

from mecks_unit.

Hey again @archan937 , can I propose as a feature for the library to give the option of choosing whether to apply the mocks to all the mocked_tests or just the first?

from mecks_unit.

Sure. I will add this later on this week. Keep an eye out! ;)

from mecks_unit.

That's great!
Thanks a lot 🙂

from mecks_unit.

Hey, @aalepis . It is a week later than promised but I have added the ability to "preserve" mock module definitions for the rest of the test case.

This has been release in MecksUnit v0.1.7 :)

For more information, please see https://github.com/archan937/mecks_unit#define-mock-module-for-entire-test-case and also 4219017

from mecks_unit.

Thank you very much @archan937, I really appreciate it!

from mecks_unit.

You're welcome, @aalepis. I hope it can help you further ;)

from mecks_unit.