| Time |
S |
Nick |
Message |
| 00:55 |
|
pdurbin |
wow, didn't expect to get a response so quickly: Philip Durbin on Twitter: "@ashton http://t.co/5OJfwRxGhC on @rubyrogues was great. Are you still looking for open source projects to run tests against? #clojure" - https://twitter.com/philipdurbin/status/575452861779173376 |
| 00:57 |
|
pdurbin |
I'm reacting to "having an example in the public domain or in the open source world will be massively useful" at http://devchat.cachefly.net/rubyrogues/196-rr-testing-clojure-in-ruby-with-ashton-kemerling.pdf |
| 00:59 |
|
pdurbin |
he talked all about using https://github.com/clojure/test.check (QuickCheck for Clojure) |
| 00:59 |
|
pdurbin |
this was at http://ashtonkemerling.com/blog/2014/09/25/integrating-test-dot-check-and-javascript/ |
| 00:59 |
|
pdurbin |
er, sorry. that was under "resources" |
| 01:00 |
|
pdurbin |
this is where I heard him talk about test.check: http://devchat.tv/ruby-rogues/196-rr-testing-clojure-in-ruby-with-ashton-kemerling |
| 01:03 |
|
pdurbin |
'generative testing... It’s like, “Oh, we’ll show you this awesome theoretical thing.” But frankly, no one cares, or very few people care.... I care if my application works.' |
| 03:54 |
|
sivoais |
pdurbin: thanks for these links. I was just thinking about QuickCheck for testing PDL. |
| 03:55 |
|
sivoais |
it's mathematical, so seems perfect |
| 03:59 |
|
sivoais |
hmm, Perl 6 doesn't have a QuickCheck module yet... |
| 04:03 |
|
sivoais |
I thought they might have used it back when Perl 6 was developed in Haskell with Pugs |
| 10:40 |
|
pdurbin |
sivoais: you see what this guy is offering? How he's looking for an open source project to add tests to? |
| 16:11 |
|
* sivoais |
skims through transcript |
| 16:20 |
|
sivoais |
hahah, the comment about Google naming things after already used and similar words: Closure, Chrome, etc. |
| 16:25 |
|
pdurbin |
yeah |
| 16:34 |
|
* sivoais |
didn't skim... |
| 16:34 |
|
* sivoais |
read the whole thing... :-P |
| 16:34 |
|
pdurbin |
:) |
| 16:39 |
|
sivoais |
responded in that Twitter thread :-) |
| 16:43 |
|
sivoais |
one of the problems that I've had at the back of my mind for a couple years is how to test scientific code |
| 16:45 |
|
sivoais |
I was reading through "Software Carpentry: lessons learned" <http://f1000research.com/articles/3-62/v1> where Greg says |
| 16:45 |
|
sivoais |
"We also don’t as good a job as we would like teaching testing. The mechanics of unit testing with an xUnit-style framework are straightforward, and it’s easy to come up with representative test cases for things like reformatting data files, but what should we tell scientists about testing the numerical parts of their applications?" |
| 16:46 |
|
sivoais |
so attempting to improve PDL's test suite is a good way for me to try to answer that |
| 16:48 |
|
pdurbin |
sure, generative testing would probably help |
| 23:54 |
|
pdurbin |
sivoais: if he replies please let me know |
