keskiviikko 9. marraskuuta 2016 2.25.59 UTC Steve D'Aprano kirjoitti:
> On Wed, 9 Nov 2016 10:01 am, teppo...@gmail.com wrote:
>
> > Generally, with testing, it would be optimal to test outputs of the system
> > for given inputs without caring how things are implemented.
>
> I disagree with that
> How is having 15 arguments in a .create() method better than having 15
> arguments in __init__() ?
> So, if you use the create() method, and it sets up internal data structures,
> how do you test them? In other words, if create() makes that queue then how
> do you test with a half-empty queue
torstai 3. marraskuuta 2016 14.47.18 UTC Chris Angelico kirjoitti:
> On Thu, Nov 3, 2016 at 7:50 PM, wrote:
> > Little bit background related to this topic. It all starts from this
> > article:
> > http://misko.hevery.com/attachments/Guide-Writing%20Testable%20Code.pdf
> >
> > The guide is writt
torstai 3. marraskuuta 2016 14.45.49 UTC Ethan Furman kirjoitti:
> On 11/03/2016 01:50 AM, teppo wrote:
>
> > The guide is written in c++ in mind, yet the concepts stands for any
> > programming language really. Read it through and think about it. If
> > you come back to this topic and say: "yea
Hello everyone, I'll step into conversation too as I think it is quite
important topic. I'd be the one my collegue calls keen to this practice.
Little bit background related to this topic. It all starts from this article:
http://misko.hevery.com/attachments/Guide-Writing%20Testable%20Code.pdf
Th
