Re^6: debug output from TODO with Test::More

"TODO tests are an extremely valuable tool when you are dealing with volatile data."

Hence why you mock the service and provide data that is not volatile.

"If it's something the programmer hasn't done yet, use TODO."

Nah, SKIP does that much better. But thanks for your opinion. Meanwhile, the real world calls ...

Comment on Re^6: debug output from TODO with Test::More

Replies are listed 'Best First'.
Re^7: debug output from TODO with Test::More by 1nickt (Canon) on Jan 14, 2017 at 02:23 UTC
Your ignorance may feel like bliss, but you are not even half as clever as you think you are. Mocking the service is the exact opposite of what is needed. You mock a service when you want to shield your test from the volatility of the data. I am running tests precisely to observe when the data changes. `TODO` is the right tool for that job, clueless though you may be about the job and the tool. The way forward always starts with a minimal test.	[reply] [d/l]

Replies are listed 'Best First'.

Re^7: debug output from TODO with Test::More
by 1nickt (Canon) on Jan 14, 2017 at 02:23 UTC

Your ignorance may feel like bliss, but you are not even half as clever as you think you are. Mocking the service is the exact opposite of what is needed. You mock a service when you want to shield your test from the volatility of the data. I am running tests precisely to observe when the data changes. TODO is the right tool for that job, clueless though you may be about the job and the tool.

The way forward always starts with a minimal test.

[reply]
[d/l]