craftytrickster / mock_me Goto Github PK

if the mock_me_context lookup was made to have multi values (perhaps the value can be the name of the test_fn, etc), instead of a single key -> value, perhaps we can avoid the issue of tests clobbering each other.

Repro step:

1. Make sure your CPU has ≥2 cores.
2. cargo test --test test
3. The test will fail most of the time.

The problem is that test_with_silly_func_1 and test_with_silly_func_2 will both modify the same _mock_me_test_context_instance. Now imagine the following sequence:

Tested with mock_me = "0.2.2" on crates.io.

$ rustc -vV
rustc 1.21.0-nightly (e26688824 2017-08-27)
binary: rustc
commit-hash: e2668882406b68739c6ed33d420358d5d710e67b
commit-date: 2017-08-27
host: x86_64-apple-darwin
release: 1.21.0-nightly
LLVM version: 4.0

Perhaps the syn crate has functionality to do so

Currently, we are forcing the programmer that is mocking the function to write the function signature. I would like this to be inferred automatically. I am not sure how this can be done, perhaps scanning the source code itself for the function could be a (somewhat crazy) viable approach.

Currently, I am using very primitive means to extract the values that I would like into the InjectMatch and MockMatch structs. This should be done in a less error prone and more structured way.

Perhaps a consumer may want to specify in which cfgs the mocked replacement is applied.

Currently, in lib.rs, in the mock and inject functions, we are inserting to code to enable this crate's functionality. I am purposely using long, uncommon names like _mock_me_test_context_instance, however, in theory there could be a name collision if the user has an identically named variable. We should figure out a way to make such a collision impossible.

Add ability to lookup which args were passed to mocked function in order to confirm test went through, as well as the ability to see how many times it was called.