I must hunt down and learn to use a QuickCheck-like library for my language. If I can't find one, I should write one. So what's the (best) equivalent of QuickCheck in Ruby? In other languages?
Go has a QuickCheck-like package distributed with it. It's under testing/quick.
Can anyone comment on the claim "QuickCheck is shockingly more effective at finding bugs than unit tests"? I'd be interested in hearing other opinions.
I haven't used QuickCheck, but read about it. So take this with a grain of salt, but it seems to me that specifying properties that should hold for your functions and then letting QuickCheck throw all kinds of data at them would be more efficient at least, if not more effective, than manually writing a bunch of unit tests and coming up with your own test data.
That said, this is pretty poorly designed. I also had no clue what to do for the first few seconds after I clicked the link. It was only at slide 38/41 that I noticed the tiny, hidden controls on the very bottom blending into my status bar.
I didn't even notice those. Fortunately, I've worked with systems like S5 slideshows, and this looked a lot like a slideshow (no scroll bar, large text, numeric fragment in the URL). Usability could definitely be better, but I will admit to writing up similarly boring slides in the past.
I must hunt down and learn to use a QuickCheck-like library for my language. If I can't find one, I should write one. So what's the (best) equivalent of QuickCheck in Ruby? In other languages?
I didn't even notice those. Fortunately, I've worked with systems like S5 slideshows, and this looked a lot like a slideshow (no scroll bar, large text, numeric fragment in the URL). Usability could definitely be better, but I will admit to writing up similarly boring slides in the past.
Compare this slideshow to the basic S5 slideshow at http://meyerweb.com/eric/tools/s5/s5-intro.html . A simple CSS template could solve the usability problem here.
I wonder why 280slides never really took off. This still seems like an unsolved problem (hosting slides online)
For background, Bryan gave this talk at the excellent Strange Loop 2011 conference ( https://thestrangeloop.com/ ). Abstract: https://thestrangeloop.com/sessions/running-a-startup-on-has... He also gave a workshop on Sunday (which I unfortunately was not able to attend): https://thestrangeloop.com/sessions/haskell-functional-progr...
For a different type of background, Bryan O'Sullivan is the author of some of the best Haskell libraries out there. The de facto standard JSON parser/serializer is his doing, for example, and his Riak client is the best I've seen in any language. This guy really knows what he's talking about.
Can anyone comment on the claim "QuickCheck is shockingly more effective at finding bugs than unit tests"? I'd be interested in hearing other opinions.
It's surprising how often people overlook weird edge cases that QuickCheck finds, because it doesn't have as many preconceptions about what kinds of inputs are sensible.