|go ahead... be a heretic|
Re: Now released: Assert::Refute - A unified testing and assertion toolby stevieb (Abbot)
|on Jan 02, 2018 at 22:42 UTC||Need Help??|
Very nice work! This is in Meditations, so I hope you don't mind some questions/feedback...
I've definitely run into that, and although sometimes it isn't feasible (read: legacy code), bloated_untestable_method() should be re-written into underlying functionality-based subs that can be tested. I digress for the purposes of your work here.
Now, I see you peeking into the innards of the object here, so it screams loudly that things should be further broken up with accessors that can be tested. This is kind of related to the above statement, and for similar reasons. Tests/assertions like this scream to me that further work needs to be done on the particulars of the object innards:
Personally, I am one who really, *really* tries to stay as close to core as possible, unless there's a significant reason for not doing so (eg. a really good existing wheel, perhaps the one you wrote here), so I'm wondering if this distribution is meant for new code, or for aiding the writing of a test regimen for legacy/existing code.
I'll even go one step further to be a pain in your ass ;) Can you please lay out examples of the following statements for my, and future readers' purposes?
I promise I am not trying to be a smartass or cause you issues. I have App::RPi::EnvUI that has so many moving parts, I *do* have code within the modules that mock, test and otherwise have to perform ridiculous procedures when it understands it is in either prod mode or test mode, so I'm looking for something to make my life simpler, and would largely appreciate a more thorough understanding of how I can use your distribution (ie. here's a good example of how you can sell it).
Again, great work. Your documentation appears clean and concise (although I haven't tested it so I can't confirm its efficacy), and the code (after a very quick glance) looks nice and clean, and with comments sparsely populated where it makes sense.
Do you have a real world example to display which made you decide to write this distribution?