2/ My rationale is that this makes the test more self-documenting and -- critically -- facilitates the separation of "what" the target does and "how" it does it. By being pedantic, you can skip subsequently looking at the implementation, which encourages comprehensible code.
1/ RFC: I recently started writing my unit tests with, target_func(param_1=x, param_2=y) instead of target_func(param_1, param_2)
-
-
Show this thread
-
3/ It also has the effect of testing the bindings as an API, but I think that's actually a negative unless you really want it to function as a keyword based api. Thoughts?
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.